Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The libcrux-ml-dsa crate, versions before 0.0.8, checks the signer response norm incorrectly during signature verification, so it accepts signatures that a conforming ML-DSA implementation would reject. An attacker who can supply signatures to a verifier can get these non-conforming signatures accepted, which the source describes as a verification-acceptance issue with no further impact listed. Upgrade to libcrux-ml-dsa 0.0.8 or later, which uses the correct value in this check.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| Not published | None | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 15:18 UTC First seen by agentprime
- 31 Oct 2026, 15:18 UTC Confirmed by OSV