{"answers":{"affected":"1 open source package ship an affected version, including zstd.","exploited":"There is no known exploitation of RUSTSEC-2026-0393 in the wild and no public exploit code.","fix":"Upgrade zstd to 0.4.10 or later.","what":"RUSTSEC-2026-0393 is a vulnerability in zstd, published on 16 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0393 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0393 is a vulnerability in zstd, published on 16 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0393 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zstd (crates.io): affected from 0.1.1; fixed in 0.4.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-0393/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0393/index.md)","id":"RUSTSEC-2026-0393","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0393/index.md","name":"RUSTSEC-2026-0393","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`ZDICT_trainFromBuffer` is never told the length of the samples buffer.\nBefore 0.4.10, `zstd::dict::from_continuous` (initially `train_dict`) called\nit directly: up to 0.2.1 without checking the sample sizes against the\nbuffer at all, and from 0.3.0 with a sum that wraps around when overflow\nchecks are off, as in release builds. Sizes that do not describe the buffer\nmade the trainer read past its end.\n\nThis requires the sample sizes to come from an untrusted source. From\n0.4.10, training goes through zstd-safe, where the same flaw is covered by\nthe zstd-safe advisory for it, fixed in zstd-safe 8.2.0.","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":"Out-of-bounds read when training a dictionary from inconsistent sample sizes","id":"RUSTSEC-2026-0393","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":["0.4.10"],"introduced":["0.1.1"],"last_affected":[],"package":"zstd","purl":"pkg:cargo/zstd","source":"RUSTSEC-2026-0393"}],"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-0393/"}