ML-KEM does not perform the FIPS 203 input checks
No exploitation in the wild has been reported. No fixed version is recorded.
`pqcrypto-mlkem` wraps PQClean's ML-KEM implementation, which does not perform the input checks required by FIPS 203: - encapsulation does not perform the encapsulation key modulus check (section 7.2), so encapsulation keys with coefficients that are not reduced modulo q are accepted; - decapsulation does not perform the decapsulation key hash check (section 7.3), so a decapsulation key whose stored hash or embedded encapsulation key has been altered is accepted. With the Wycheproof ML-KEM vectors, 108 / 112 / 116 invalid encapsulation keys (ML-KEM-512 / -768 / -1024) and 2 invalid decapsulation keys per parameter set are accepted. This does not disclose key material. It is a FIPS 203 non-conformance, and an affected implementation can disagree with a conforming one about which keys are valid. The crate is unmaintained (see RUSTSEC-2026-0161) and no patched version is expected. Migrating to a maintained implementation, such as the [`ml-kem`](https://crates.io/crates/ml-kem) crate, is recommended.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| cargo: pqcrypto-mlkem | >=0.0.0-0 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket