How severe is GHSA-xpww-g9jx-hp8r?

No CVSS score has been assigned to GHSA-xpww-g9jx-hp8r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xpww-g9jx-hp8r?

GHSA-xpww-g9jx-hp8r affects the following packages: sha2 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-xpww-g9jx-hp8r?

Update sha2 to 0.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xpww-g9jx-hp8r is resolved across your whole dependency graph.

How do I detect GHSA-xpww-g9jx-hp8r in my crates.io dependencies?

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

How do I mitigate GHSA-xpww-g9jx-hp8r 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.

How does O3 Security protect against GHSA-xpww-g9jx-hp8r?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xpww-g9jx-hp8r can be triaged on real exposure rather than presence alone.

Is GHSA-xpww-g9jx-hp8r actively exploited in the wild?

No public exploit code has been indexed for GHSA-xpww-g9jx-hp8r 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.

What is the EPSS score for GHSA-xpww-g9jx-hp8r?

GHSA-xpww-g9jx-hp8r has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xpww-g9jx-hp8r?

GHSA-xpww-g9jx-hp8r is classified as Broken Cryptographic Algorithm (CWE-327). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xpww-g9jx-hp8r published, and has it been updated?

GHSA-xpww-g9jx-hp8r was published on June 17, 2022 and was last updated on November 8, 2023. 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

GHSA-xpww-g9jx-hp8r — sha2

Fix: RustCrypto/hashes#314

GHSA-xpww-g9jx-hp8r is a Broken Cryptographic Algorithm vulnerability in sha2. A fix is available for sha2 — see the affected versions and patch details below.

Miscomputed sha2 results when using AVX2 backend

Also known asCVE-2021-45696 GHSA-fc7x-2cmc-8j2gRUSTSEC-2021-0100

Published

Jun 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🦀sha2

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

The v0.9.7 release of the sha2 crate introduced a new AVX2-accelerated backend which was automatically enabled for all x86/x86_64 CPUs where AVX2 support was autodetected at runtime.

This backend was buggy and would miscompute results for long messages (i.e. messages spanning multiple SHA blocks).

The crate has since been yanked, but any users who upgraded to v0.9.7 should immediately upgrade to v0.9.8 and recompute any hashes which were previously computed by v0.9.7.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`sha2`	≥ 0.9.7&&< 0.9.8	0.9.8`cargo update -p sha2 --precise 0.9.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sha2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sha2 to 0.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xpww-g9jx-hp8r 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xpww-g9jx-hp8r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xpww-g9jx-hp8r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The v0.9.7 release of the `sha2` crate introduced a new AVX2-accelerated backend which was automatically enabled for all x86/x86_64 CPUs where AVX2 support was autodetected at runtime. This backend was buggy and would miscompute results for long messages (i.e. messages spanning multiple SHA blocks). The crate has since been yanked, but any users who upgraded to v0.9.7 should immediately upgrade to v0.9.8 and recompute any hashes which were previously computed by v0.9.7.

O3 Security · Impact-Aware SCA

Is GHSA-xpww-g9jx-hp8r in your dependencies?

O3 Security finds GHSA-xpww-g9jx-hp8r across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works