Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0126 json

AVX2 Implementation Did Not Fully Reduce Intermediate Values

published 6mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io libcrux-ml-dsa 0.0.9

Is RUSTSEC-2026-0126 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io libcrux-ml-dsa
>=0.0.0-0, <0.0.9
0.0.9

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.