Miscomputed sha2 results when using AVX2 backend
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed sha2 (crates.io): 0.9.8
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | sha2 (crates.io) | 0.9.7 to before 0.9.8 | 0.9.8 | Patch available | GHSA-xpww-g9jx-hp8r |
- sha2 (crates.io) Vendor— Affected 0.9.7 to before 0.9.8 Fixed in 0.9.8 Patch available GHSA-xpww-g9jx-hp8r
Remediation
- Fix · GHSA-xpww-g9jx-hp8r sha2 (crates.io) Fixed in 0.9.8 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-xpww-g9jx-hp8r
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences