RUSTSEC-2025-0055: Logging user input may result in poisoning logs with ANSI escape sequences

What to do

1. See which version you have: cargo tree -i tracing-subscriber (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p tracing-subscriber. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example tracing-subscriber = "0.3.20") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

• Manipulate terminal title bars
• Clear screens or modify terminal display
• Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

This was patched in PR #3368 to escape ANSI control characters from user input.

References

• Package: crates.io/crates/tracing-subscriber
• Advisory: rustsec.org/advisories/RUSTSEC-2025-0055.html
• Web: github.com/tokio-rs/tracing/pull/3368

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.