How severe is GHSA-cp57-fq8g-qh6v?

No CVSS score has been assigned to GHSA-cp57-fq8g-qh6v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cp57-fq8g-qh6v?

GHSA-cp57-fq8g-qh6v affects the following packages: libcrux-ml-dsa (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-cp57-fq8g-qh6v?

Update libcrux-ml-dsa to 0.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cp57-fq8g-qh6v is resolved across your whole dependency graph.

How do I detect GHSA-cp57-fq8g-qh6v in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-ml-dsa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cp57-fq8g-qh6v if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-cp57-fq8g-qh6v actively exploited in the wild?

No public exploit code has been indexed for GHSA-cp57-fq8g-qh6v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-cp57-fq8g-qh6v published, and has it been updated?

GHSA-cp57-fq8g-qh6v was published on March 26, 2026 and was last updated on March 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

libcrux has an Incorrect Check of Signer Response Norm During VerificationGHSA-cp57-fq8g-qh6v

Fix: cryspen/libcrux#1347

GHSA-cp57-fq8g-qh6v is a remote code execution vulnerability in libcrux-ml-dsa. A fix is available for libcrux-ml-dsa — see the affected versions and patch details below.

Also known asRUSTSEC-2026-0077

Published

Mar 26, 2026

Updated

Mar 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 27, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀libcrux-ml-dsa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libcrux-ml-dsa`	all versions	0.0.8`cargo update -p libcrux-ml-dsa --precise 0.0.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libcrux-ml-dsa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libcrux-ml-dsa to 0.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cp57-fq8g-qh6v is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

The ML-DSA verification algorithm as specified in [FIPS 204, subsection 6.3](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.pdf#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 Ap

O3 Security · Impact-Aware SCA

Is GHSA-cp57-fq8g-qh6v in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works