How severe is GHSA-2rxc-gjrp-vjhx?

No CVSS score has been assigned to GHSA-2rxc-gjrp-vjhx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2rxc-gjrp-vjhx?

GHSA-2rxc-gjrp-vjhx affects the following packages: anstream (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-2rxc-gjrp-vjhx?

Update anstream to 0.6.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2rxc-gjrp-vjhx is resolved across your whole dependency graph.

How do I detect GHSA-2rxc-gjrp-vjhx in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for anstream, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2rxc-gjrp-vjhx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2rxc-gjrp-vjhx actively exploited in the wild?

No public exploit code has been indexed for GHSA-2rxc-gjrp-vjhx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2rxc-gjrp-vjhx published, and has it been updated?

GHSA-2rxc-gjrp-vjhx was published on December 4, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Unsoundness in anstreamGHSA-2rxc-gjrp-vjhx

GHSA-2rxc-gjrp-vjhx is a security vulnerability in anstream. A fix is available for anstream — see the affected versions and patch details below.

Also known asRUSTSEC-2024-0404

Published

Dec 4, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀anstream

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80.

When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence.

This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen.

Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`anstream`	all versions	0.6.8`cargo update -p anstream --precise 0.6.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for anstream, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update anstream to 0.6.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2rxc-gjrp-vjhx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

When given a valid UTF8 string "ö\x1b😀", the function in crates/anstream/src/adapter/strip.rs will be confused. The UTF8 bytes are \xc3\xb6 then \x1b then \xf0\x9f\x98\x80. When looping over "non-printable bytes" \x1b\xf0 will be considered as some non-printable sequence. This will produce a broken str from the incorrectly segmented bytes via str::from_utf8_unchecked, and that should never happen. Full credit goes to @Ralith who reviewed this code and asked @burakemir to follow up.

O3 Security · Impact-Aware SCA

Is GHSA-2rxc-gjrp-vjhx in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works