What is GHSA-XPWW-G9JX-HP8R?

GHSA-XPWW-G9JX-HP8R is a high-severity security vulnerability in sha2 (rust), affecting versions = 0.9.7. It is fixed in 0.9.8.

Which versions of sha2 are affected by GHSA-XPWW-G9JX-HP8R?

sha2 (rust) versions = 0.9.7 is affected.

Is there a fix for GHSA-XPWW-G9JX-HP8R?

Yes. GHSA-XPWW-G9JX-HP8R is fixed in 0.9.8. Upgrade to this version or later.

Is GHSA-XPWW-G9JX-HP8R exploitable, and should I be worried?

Whether GHSA-XPWW-G9JX-HP8R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-XPWW-G9JX-HP8R is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-XPWW-G9JX-HP8R in sha2

Q: How do I fix GHSA-XPWW-G9JX-HP8R?

Upgrade sha2 to 0.9.8 or later.

Summary

Miscomputed sha2 results when using AVX2 backend

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.

Impact

Affected versions

sha2 (= 0.9.7)

Security releases

sha2 → 0.9.8 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade sha2 to 0.9.8 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-XPWW-G9JX-HP8R? GHSA-XPWW-G9JX-HP8R is a high-severity security vulnerability in sha2 (rust), affecting versions = 0.9.7. It is fixed in 0.9.8.
Which versions of sha2 are affected by GHSA-XPWW-G9JX-HP8R? sha2 (rust) versions = 0.9.7 is affected.
Is there a fix for GHSA-XPWW-G9JX-HP8R? Yes. GHSA-XPWW-G9JX-HP8R is fixed in 0.9.8. Upgrade to this version or later.
Is GHSA-XPWW-G9JX-HP8R exploitable, and should I be worried? Whether GHSA-XPWW-G9JX-HP8R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-XPWW-G9JX-HP8R is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-XPWW-G9JX-HP8R? Upgrade sha2 to 0.9.8 or later.

Other vulnerabilities in sha2

CVE-IDSeverityPackage summary

CVE-2021-45696Criticalsha2: Incorrect hash in sha2