Advisory

GHSA-cp57-fq8g-qh6v

Also known as: RUSTSEC-2026-0077

Summary

libcrux has an Incorrect Check of Signer Response Norm During Verification

Details

The ML-DSA verification algorithm as specified in FIPS 204, subsection 6.3 requires verifiers to check that the infinity norm of the deserialized signer response $z$ does not exceed $\gamma_1 - \beta$ (line 13 of Algorithm 8). The same check is required to be performed during signature generation.

libcrux-ml-dsa did not perform this check correctly during signature verification, accepting signatures with signer response norm above the allowed maximum value. The check is correctly performed during signing.

Impact
Applications using libcrux-ml-dsa for signature verification would have accepted signatures that would be rejected by a conforming implementation.

Mitigation
Starting from version 0.0.8, signature verification uses the correct value for $\gamma_1$ in the signer response norm check.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-03-26 18:00 UTC
Modified
2026-03-27 06:11 UTC

Affected packages and fixes

libcrux-ml-dsa

crates.io · All systems

Affected

  • introduced 0, fixed 0.0.8 (semver)

Fixed versions

0.0.8

Fix

  • Fixed version 0.0.8
    cargo update -p libcrux-ml-dsa --precise 0.0.8

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences