GHSA-cp57-fq8g-qh6v: Libcrux ml dsa Libcrux Has An Incorrect Check Vulnerability

HIGH
Share
CWE-347
Published
Advisory Summary

GHSA-cp57-fq8g-qh6v is a HIGH libcrux has an incorrect check vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Libcrux ml dsa libraries in the crates.io ecosystem. The issue involves libcrux has an incorrect check of signer response norm during verification. Remediation is available by upgrading affected packages to version 0.0.8.

GHSA-cp57-fq8g-qh6v at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-cp57-fq8g-qh6v
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Libcrux ml dsa
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-cp57-fq8g-qh6v

To remediate this vulnerability, upgrade all affected Libcrux ml dsa dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

libcrux-ml-dsa fixed: 0.0.8 
Upgrade libcrux-ml-dsa to 0.0.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for libcrux-ml-dsa

How to Check if You Are Affected

To determine whether your application is affected by GHSA-cp57-fq8g-qh6v, inspect your project dependencies for Libcrux ml dsa:

inspect dependencies for libcrux-ml-dsa

Analyze the terminal output to locate any version of Libcrux ml dsa in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Libcrux ml dsa, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 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.

GHSA-cp57-fq8g-qh6v Affected Libcrux ml dsa Versions

1 component(s)
Fixed Versions:
0.0.8
Product / Package Ecosystem Affected Versions Fixed Version
libcrux-ml-dsa
 crates.io
< 0.0.8
0.0.8

References

Libcrux ml dsa Source Repository REPOSITORY
https://github.com/cryspen/libcrux/pull/1347
Libcrux ml dsa Source Repository REPOSITORY
https://github.com/cryspen/libcrux
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2026-0077.html

Frequently Asked Questions

What is GHSA-cp57-fq8g-qh6v?
GHSA-cp57-fq8g-qh6v is a security vulnerability in Libcrux ml dsa involving libcrux has an Incorrect Check of Signer Response Norm During Verification under CWE-347: Improper Verification of Cryptographic Signature.
Which Libcrux ml dsa versions are affected?
Affected versions include releases prior to 0.0.8 across affected packages: libcrux-ml-dsa.
What version fixes GHSA-cp57-fq8g-qh6v?
Upgrading to 0.0.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is libcrux-ml-dsa affected?
Yes, libcrux-ml-dsa is affected in releases prior to 0.0.8. Upgrade your dependency to 0.0.8 or later.
What CWE is associated with GHSA-cp57-fq8g-qh6v?
GHSA-cp57-fq8g-qh6v is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check crates.io dependencies for GHSA-cp57-fq8g-qh6v?
Run the dependency tree command: 'inspect dependencies for libcrux-ml-dsa'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cp57-fq8g-qh6v",
  "modified" : "2026-03-26T18:00:28Z",
  "published" : "2026-03-26T18:00:28Z",
  "aliases" : [ ],
  "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](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.\n\nlibcrux-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.\n\n## Impact\nApplications using libcrux-ml-dsa for signature verification would have accepted signatures that would be rejected by a conforming implementation.\n\n## Mitigation\nStarting from version `0.0.8`, signature verification uses the correct value for $\\gamma_1$ in the signer response norm check.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "libcrux-ml-dsa"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cryspen/libcrux/pull/1347"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cryspen/libcrux"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2026-0077.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-26T18:00:28Z",
    "nvd_published_at" : null
  }
}