Tracing logging user input may result in poisoning logs with ANSI escape sequences

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-58160: 0.34% estimated exploitation activity in the next 30 days; percentile 27.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: - 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. Patches tracing-subscriber 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. 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…

Published by the source

29 Aug 2025, 20:33 UTC

Last modified by the source

2 Sep 2025, 16:35 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xwfj-jgwm-7wp5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-58160

Advisory: Tracing logging user input may result in poisoning logs with ANSI escape sequences
IDs: CVE-2025-58160, GHSA-xwfj-jgwm-7wp5
Record: https://patchnext.com/advisories/cve-2025-58160 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tracing-subscriber 0.3.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tracing-subscriber: affected < 0.3.20; fixed in 0.3.20

## Suggested inspection (read-only)
- crates.io tracing-subscriber: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tracing-subscriber.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xwfj-jgwm-7wp5 (GitHub-reviewed advisory GHSA-xwfj-jgwm-7wp5 lists affected ranges: crates.io tracing-subscriber >=0 <0.3.20)

Commands are suggestions: review each one before running it.