{"answers":{"affected":"1 open source package ship an affected version, including libcrux-sha3.","exploited":"There is no known exploitation of RUSTSEC-2026-0208 in the wild and no public exploit code.","fix":"Upgrade libcrux-sha3 to 0.0.10 or later.","what":"RUSTSEC-2026-0208 is a denial of service vulnerability in libcrux-sha3, published on 21 May 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0208 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0208 is a denial of service vulnerability in libcrux-sha3, published on 21 May 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0208 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-0208/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0208/index.md)","id":"RUSTSEC-2026-0208","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0208/index.md","name":"RUSTSEC-2026-0208","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust cryptographic library","requires_auth":"none","summary":"A panic in the AVX2 SHAKE-256 implementation allows denial of service when using specific output buffer lengths outside standard ML-KEM/ML-DSA usage.","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":"The AVX2-optimized implementation of SHAKE-256 intended for use in\nML-KEM and ML-DSA would panic if the length of the output buffers was\ngreater than 32 and not a multiple of 8, due to an out-of-bounds\nindexing operation.\n\n## Impact\nThis bug impacts users on AVX2 platforms that use the\n`libcrux_sha3::avx2::x4::shake256` API outside of ML-KEM or ML-DSA\nwith output buffers of length `\u003e 32` and not divisible by `8`. It does\nnot impact the use in ML-KEM or ML-DSA because there output buffer\nlengths are always divisible by `8`.\n\n## Mitigation\nStarting from version `0.0.10`, the AVX2-optimized SHAKE-256 will no\nlonger panic on output buffer lengths `\u003e 32` that are not divisible by\n`8`.","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":"Potential Panic in AVX2 SHAKE-256","id":"RUSTSEC-2026-0208","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","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-0208"}],"products":null,"published":"2026-05-21","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":"A panic in the AVX2 SHAKE-256 implementation allows denial of service when using specific output buffer lengths outside standard ML-KEM/ML-DSA usage.","url":"https://insights.sbomify.com/RUSTSEC-2026-0208/"}