{"answers":{"affected":"1 open source package ship an affected version, including zstd-sys.","exploited":"There is no known exploitation of RUSTSEC-2026-0410 in the wild and no public exploit code.","fix":"Upgrade zstd-sys to 2.1.2 or later.","what":"RUSTSEC-2026-0410 is a vulnerability in zstd-sys, published on 16 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0410 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0410 is a vulnerability in zstd-sys, published on 16 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0410 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zstd-sys (crates.io): affected from 2.0.9; fixed in 2.1.2\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-0410/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0410/index.md)","id":"RUSTSEC-2026-0410","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0410/index.md","name":"RUSTSEC-2026-0410","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"On wasm32, zstd-sys provides `malloc` and `free` to the C library through a\nshim over Rust's allocator. The shim did not check for allocation failure:\nit wrote its size header to address 0 and returned address 4, which the C\nlibrary used as a valid buffer. `free(NULL)` also read below address 0.\n\nWhenever the instance cannot grow its memory by what a frame asks for, a\nsmall crafted frame (a 9-byte header declaring a 128 MiB window is enough)\nmade decompression write decoded data over the bottom of the module's\nlinear memory, instead of failing. The corruption stays within the wasm\nsandbox.\n\nThe flaw was corrected by returning NULL on allocation failure or size\noverflow, and by making `free(NULL)` a no-op.","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":"WebAssembly allocator shim corrupts memory on allocation failure","id":"RUSTSEC-2026-0410","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["2.1.2"],"introduced":["2.0.9"],"last_affected":[],"package":"zstd-sys","purl":"pkg:cargo/zstd-sys","source":"RUSTSEC-2026-0410"}],"products":null,"published":"2026-10-16","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":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0410/"}