chore(deps): update rust crate tracing-subscriber to v0.3.20 [security]#36
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update rust crate tracing-subscriber to v0.3.20 [security]#36renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
October 14, 2025 18:46
740963e to
909b3fc
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
December 12, 2025 00:12
909b3fc to
bf61b5a
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
December 31, 2025 15:30
bf61b5a to
6dd6679
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
February 2, 2026 21:49
6dd6679 to
398072b
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
February 12, 2026 18:00
398072b to
47d1ae9
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
February 25, 2026 12:56
47d1ae9 to
e42004e
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
March 13, 2026 15:14
e42004e to
58af428
Compare
renovate
Bot
deleted the
renovate/crate-tracing-subscriber-vulnerability
branch
March 27, 2026 01:14
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
2 times, most recently
from
March 31, 2026 02:06
58af428 to
fbe8669
Compare
renovate
Bot
force-pushed
the
renovate/crate-tracing-subscriber-vulnerability
branch
from
May 18, 2026 10:15
fbe8669 to
01a832c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.3.19→0.3.20Tracing logging user input may result in poisoning logs with ANSI escape sequences
CVE-2025-58160 / GHSA-xwfj-jgwm-7wp5
More information
Details
Impact
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:
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.
Patches
tracing-subscriberversion 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.Workarounds
Avoid printing logs to terminal emulators without escaping ANSI control sequences.
References
https://www.packetlabs.net/posts/weaponizing-ansi-escape-sequences/
Acknowledgments
We would like to thank zefr0x who responsibly reported the issue at
security@tokio.rs.If you believe you have found a security vulnerability in any tokio-rs project, please email us at
security@tokio.rs.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
tokio-rs/tracing (tracing-subscriber)
v0.3.20: tracing-subscriber 0.3.20Compare Source
Security Fix: ANSI Escape Sequence Injection (CVE-TBD)
Impact
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:
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.
Solution
Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.
Affected Versions
All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.
Recommendations
Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:
Migration
This is a patch release with no breaking API changes. Simply update your Cargo.toml:
Acknowledgments
We would like to thank zefr0x who responsibly reported the issue at
security@tokio.rs.If you believe you have found a security vulnerability in any tokio-rs project, please email us at
security@tokio.rs.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.