{"answers":{"affected":"3 open source packages ship an affected version, including libcrux-sha3.","exploited":"There is no known exploitation of GHSA-q29p-9pfr-j652 in the wild and no public exploit code.","fix":"Upgrade libcrux-sha3 to 0.0.8 or later.","what":"GHSA-q29p-9pfr-j652 is a vulnerability in libcrux-sha3, published on 4 Mar 2026."},"fix_prompt":"Check this codebase for GHSA-q29p-9pfr-j652 and fix it if it is affected.\n\nWhat it is: GHSA-q29p-9pfr-j652 is a vulnerability in libcrux-sha3, published on 4 Mar 2026. \nExploitation: There is no known exploitation of GHSA-q29p-9pfr-j652 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libcrux-sha3 (crates.io): affected all versions; fixed in 0.0.8\n- libcrux-sha3 (crates.io): affected all versions; fixed in 0.0.8\n- libcrux-sha3 (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-q29p-9pfr-j652/ (Markdown: https://insights.sbomify.com/GHSA-q29p-9pfr-j652/index.md)","id":"GHSA-q29p-9pfr-j652","markdown":"https://insights.sbomify.com/GHSA-q29p-9pfr-j652/index.md","name":"GHSA-q29p-9pfr-j652","record":{"aliases":["RUSTSEC-2026-0074"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust SHAKE library","requires_auth":"none","summary":"Incorrect output generation in the SHAKE XOF API when squeezing large amounts of data, potentially leading to invalid cryptographic results.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The incremental squeeze functions in the portable SHAKE XOF API, when\n attempting to squeeze more than `RATE` (168 for SHAKE128, 136 for\n SHAKE256) bytes, performed an additional permutation of the state\n before producing the first output block, thus discarding the first\n block of `RATE` bytes of valid XOF output.\n\n## Impact\nThis bug impacts users that rely on this XOF API to squeeze more than\n`RATE` bytes. It does not impact the use of libcrux-sha3 in\nlibcrux-ml-kem or libcrux-ml-dsa.\n\n## Mitigation\nStarting from version `0.0.8` the squeeze functions correctly output\nall blocks including the first block.","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":"Incorrect Output of Incremental Portable SHAKE API","id":"GHSA-q29p-9pfr-j652","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.0.8"],"introduced":["0"],"last_affected":[],"package":"libcrux-sha3","purl":null,"source":"GHSA-q29p-9pfr-j652"},{"ecosystem":"crates.io","fixed":["0.0.8"],"introduced":["0"],"last_affected":[],"package":"libcrux-sha3","purl":"pkg:cargo/libcrux-sha3","source":"GHSA-q29p-9pfr-j652"},{"ecosystem":"crates.io","fixed":["0.0.8"],"introduced":["0.0.0-0"],"last_affected":[],"package":"libcrux-sha3","purl":"pkg:cargo/libcrux-sha3","source":"RUSTSEC-2026-0074"}],"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":"Incorrect output generation in the SHAKE XOF API when squeezing large amounts of data, potentially leading to invalid cryptographic results.","url":"https://insights.sbomify.com/GHSA-q29p-9pfr-j652/"}