RUSTSEC-2026-0586: ML-DSA verification accepts non-conforming signatures with the `avx2` feature

Unknown

OSV id
RUSTSEC-2026-0586
Published
Last modified

Affected packages

PackageAffected versionsFixed in
pqcrypto-mldsa
Cargo
>= 0.0.0-0 not fixed yet

How to fix it

No fix yet. No fixed version of pqcrypto-mldsa has been released yet.

  • Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
  • Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
  • Pin away from the affected versions if an older release is not affected, or consider replacing the package.
  • Watch for the fix: a free AIssue account checks your lockfiles every day and emails you when a fixed version is released.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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, 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 crate, is recommended.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: RustSec Advisory Database via OSV.dev (CC0 1.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.