{"answers":{"affected":"1 open source package ship an affected version, including libcrux-sha3.","exploited":"There is no known exploitation of RUSTSEC-2026-0207 in the wild and no public exploit code.","fix":"Upgrade libcrux-sha3 to 0.0.10 or later.","what":"RUSTSEC-2026-0207 is a vulnerability in libcrux-sha3, published on 22 Apr 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0207 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0207 is a vulnerability in libcrux-sha3, published on 22 Apr 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0207 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libcrux-sha3 (crates.io): affected from 0.0.0-0; fixed in 0.0.10\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/RUSTSEC-2026-0207/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0207/index.md)","id":"RUSTSEC-2026-0207","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0207/index.md","name":"RUSTSEC-2026-0207","record":{"aliases":[],"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 portable SHAKE API when squeezing in multiple calls can lead to data integrity issues for dependent applications.","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\nattempting to squeeze an output using multiple calls to `squeeze`,\nrather than squeezing the full output at once, could output incorrect\nvalues. Internally, output blocks that were not completely squeezed\nwere not buffered for the next call to `squeeze`, which would\nconsequently drop bytes of the correct squeeze output if the preceding\ncall requested an output of length in bytes not cleanly divisible by\n`RATE` (168 for SHAKE128, 136 for SHAKE256).\n\n## Impact\nThis bug impacts users that rely on this XOF API to squeeze output in\nmultiple calls where any of the calls request an output length that is\nnot divisible by `RATE`. 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.10` the squeeze functions correctly output\nall squeezed bytes independent of the number of `squeeze` calls and\nthe output lengths requested in each call.","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 on Multiple Squeeze Calls","id":"RUSTSEC-2026-0207","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.0.10"],"introduced":["0.0.0-0"],"last_affected":[],"package":"libcrux-sha3","purl":"pkg:cargo/libcrux-sha3","source":"RUSTSEC-2026-0207"}],"products":null,"published":"2026-04-22","related":[],"sources":[{"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 portable SHAKE API when squeezing in multiple calls can lead to data integrity issues for dependent applications.","url":"https://insights.sbomify.com/RUSTSEC-2026-0207/"}