{"answers":{"affected":"3 open source packages ship an affected version, including libcrux-ml-dsa.","exploited":"There is no known exploitation of GHSA-xrf2-5r3p-5wgj in the wild and no public exploit code.","fix":"Upgrade libcrux-ml-dsa to 0.0.8 or later.","what":"GHSA-xrf2-5r3p-5wgj is a denial of service vulnerability in libcrux-ml-dsa, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-xrf2-5r3p-5wgj and fix it if it is affected.\n\nWhat it is: GHSA-xrf2-5r3p-5wgj is a denial of service vulnerability in libcrux-ml-dsa, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-xrf2-5r3p-5wgj in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libcrux-ml-dsa (crates.io): affected all versions; fixed in 0.0.8\n- libcrux-ml-dsa (crates.io): affected all versions; fixed in 0.0.8\n- libcrux-ml-dsa (crates.io): affected from 0.0.0-0; fixed in 0.0.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-xrf2-5r3p-5wgj/ (Markdown: https://insights.sbomify.com/GHSA-xrf2-5r3p-5wgj/index.md)","id":"GHSA-xrf2-5r3p-5wgj","markdown":"https://insights.sbomify.com/GHSA-xrf2-5r3p-5wgj/index.md","name":"GHSA-xrf2-5r3p-5wgj","record":{"aliases":["RUSTSEC-2026-0076"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust ML-DSA library","requires_auth":"none","summary":"A manipulated invalid hint in ML-DSA verification causes an out-of-bounds memory access and runtime panic, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"During ML-DSA verification the serialized hint values are decoded as specified in algorithm 22 `HintBitUnpack` of [FIPS 204, subsection 7.1](https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.204.pdf#%5B%7B%22num%22%3A120%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22FitH%22%7D%2C657%5D). The algorithm requires that the cumulative hint counters per row of the hint vector are strictly increasing and below a maximum value which depends on the choice of ML-DSA parameter set (line 4).\n\nIn libcrux-ml-dsa, hint decoding did not check the boundedness of the cumulative hint counter of the last row of the hint vector.\n\n## Impact\nA manipulated invalid hint can cause an out-of-bounds memory access since the hint decoding logic may attempt to read outside the bounds of the serialized signature, causing a runtime panic.\n\n## Mitigation\nStarting from version `0.0.8`, hint decoding will check the cumulative hint counter of the last row as well.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"libcrux: Panic in Signature Hint Decoding During Verification","id":"GHSA-xrf2-5r3p-5wgj","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.0.8"],"introduced":["0"],"last_affected":[],"package":"libcrux-ml-dsa","purl":null,"source":"GHSA-xrf2-5r3p-5wgj"},{"ecosystem":"crates.io","fixed":["0.0.8"],"introduced":["0"],"last_affected":[],"package":"libcrux-ml-dsa","purl":"pkg:cargo/libcrux-ml-dsa","source":"GHSA-xrf2-5r3p-5wgj"},{"ecosystem":"crates.io","fixed":["0.0.8"],"introduced":["0.0.0-0"],"last_affected":[],"package":"libcrux-ml-dsa","purl":"pkg:cargo/libcrux-ml-dsa","source":"RUSTSEC-2026-0076"}],"products":null,"published":"2026-03-04","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A manipulated invalid hint in ML-DSA verification causes an out-of-bounds memory access and runtime panic, leading to denial of service.","url":"https://insights.sbomify.com/GHSA-xrf2-5r3p-5wgj/"}