RUSTSEC-2026-0585: ML-KEM does not perform the FIPS 203 input checks
Unknown
- OSV id
- RUSTSEC-2026-0585
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| pqcrypto-mlkem Cargo |
>= 0.0.0-0 | not fixed yet |
How to fix it
No fix yet. No fixed version of pqcrypto-mlkem 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
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 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.
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.