RustSec logo

History ⋅ Edit ⋅ JSON (OSV)

RUSTSEC-2026-0586

ML-DSA verification accepts non-conforming signatures with the avx2 feature

Reported
Issued
Package
pqcrypto-mldsa (crates.io)
Type
Vulnerability
Categories
Keywords
#ml-dsa #signature #verification #avx2
References
Patched
no patched versions
Affected Architectures
  • x86_64
Affected Functions
Version
pqcrypto_mldsa::mldsa44::verify_detached_signature
  • <=0.1.2
pqcrypto_mldsa::mldsa65::verify_detached_signature
  • <=0.1.2
pqcrypto_mldsa::mldsa87::verify_detached_signature
  • <=0.1.2

Description

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):

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.

Advisory available under CC0-1.0 license.