Skip to content

RUSTSEC-2026-0126

AVX2 Implementation Did Not Fully Reduce Intermediate Values

Not rated yet crates.io
Severity
Not rated yet
No source has published a CVSS score yet
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
—
Not classified
Fix
0.0.9
Upgrade libcrux-ml-dsa to this version or later

Description

The AVX2 implementation of ML-DSA did not fully reduce intermediate inputs to the inverse NTT, which leads to a testable difference in panic behaviour of internal functions compared to the portable implementation.

Impact

We are not aware of inputs to the public key generation, signing or verification APIs that trigger a panic in the AVX2 implementation because the intermediate values were not fully reduced.

Mitigation

From version 0.0.9 intermediate values on AVX2 platforms are fully reduced in alignment with the portable implementation.

Affected versions

crates.io

PackageVulnerableFixed in
libcrux-ml-dsa
>= 0.0.0-0, < 0.0.9
0.0.9

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

libcrux-ml-dsa crates.io → 0.0.9

cargo
cargo update -p libcrux-ml-dsa --precise 0.0.9

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-fhvh-vw7h-9xf3
libcrux-ml-dsa: Signature Verification on AVX2 Platforms Mishandles Edge Case
High Also affects libcrux-ml-dsa
RUSTSEC-2026-0076
libcrux: Panic in Signature Hint Decoding During Verification
High Also affects libcrux-ml-dsa
GHSA-cp57-fq8g-qh6v
libcrux has an Incorrect Check of Signer Response Norm During Verification
High Also affects libcrux-ml-dsa
GHSA-2cgv-28vr-rv6j
libcrux incorrectly calculates on aarch64
High Also affects libcrux-ml-dsa
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor