RUSTSEC-2026-0586 json
ML-DSA verification accepts non-conforming signatures with the `avx2` feature
published yesterday modified yesterday
- 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
With the default `avx2` feature on x86_64 (non-Windows) and a CPU that supports AVX2, `pqcrypto-mldsa` verifies signatures with PQClean's AVX2 implementation of ML-DSA. That implementation predates two upstream fixes ([pq-crystals/dilithium#113](https://github.com/pq-crystals/dilithium/issues/113), 3 June 2026):
- the verifier does not check that the infinity norm of `z` is below `γ1 − β` (FIPS 204, Algorithm 8, line 13), so it accepts signatures that conforming verifiers reject; - `use_hint_avx()` mishandles a boundary case, so one class of valid signatures is rejected.
Creating an accepted out-of-bound signature requires the private key. The practical effect is that verification results differ between this crate with AVX2 and conforming implementations, including this crate without AVX2.
The Wycheproof ML-DSA verification vectors reproduce both defects: with AVX2, 37 / 41 / 49 invalid vectors (ML-DSA-44 / -65 / -87) are accepted and one valid vector per parameter set is rejected.
The crate is unmaintained (see RUSTSEC-2026-0166) and no patched version is expected. Disabling the `avx2` feature avoids the affected code. Migrating to a maintained implementation, such as the [`ml-dsa`](https://crates.io/crates/ml-dsa) crate, is recommended.
Is RUSTSEC-2026-0586 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | pqcrypto-mldsa | >=0.0.0-0 |
no fix listed |
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.