{"answers":{"affected":"1 open source package ship an affected version, including zstd-safe.","exploited":"There is no known exploitation of RUSTSEC-2026-0397 in the wild and no public exploit code.","fix":"Upgrade zstd-safe to 8.2.0 or later.","what":"RUSTSEC-2026-0397 is a vulnerability in zstd-safe, published on 16 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0397 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0397 is a vulnerability in zstd-safe, published on 16 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0397 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zstd-safe (crates.io): affected from 4.0.0; fixed in 8.2.0\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-0397/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0397/index.md)","id":"RUSTSEC-2026-0397","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0397/index.md","name":"RUSTSEC-2026-0397","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`OutBuffer::around_pos` accepted a position past the initialized length of a\n`Vec\u003cu8\u003e`. The next streaming call then marked everything before the\nposition as initialized, so safe code could read stale heap memory between\nthe vector's previous length and that position.\n\nThe flaw was corrected by zero-filling that gap.","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":"`OutBuffer::around_pos` exposes uninitialized memory","id":"RUSTSEC-2026-0397","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":["8.2.0"],"introduced":["4.0.0"],"last_affected":[],"package":"zstd-safe","purl":"pkg:cargo/zstd-safe","source":"RUSTSEC-2026-0397"}],"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-0397/"}