{"answers":{"affected":"1 open source package ship an affected version, including zstd.","exploited":"There is no known exploitation of RUSTSEC-2026-0392 in the wild and no public exploit code.","fix":"Upgrade zstd to 0.8.0 or later.","what":"RUSTSEC-2026-0392 is a vulnerability in zstd, published on 16 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0392 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0392 is a vulnerability in zstd, published on 16 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0392 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zstd (crates.io): affected from 0.4.22; fixed in 0.8.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-0392/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0392/index.md)","id":"RUSTSEC-2026-0392","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0392/index.md","name":"RUSTSEC-2026-0392","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"From 0.4.22 to 0.7.x, the writer behind `zstd::stream::write::Decoder` set\nits output buffer's length to its full capacity before each decompression\ncall, then to the position the call reported, and only checked for an error\nafterwards. When decompression fails inside a legacy (zstd v0.4 to v0.7)\nframe, the bundled zstd library reports the output as fully written although\nnothing was written, so stale heap memory, up to the buffer size (32 KiB by\ndefault), was passed to the wrapped writer.\n\nLegacy support is enabled by default, and a few bytes of corrupt legacy\nframe are enough. Whether this reaches an attacker depends on where the\napplication sends the decompressed output.\n\nFrom 0.8.0, the writer uses zstd-safe's buffers, and the same flaw there is\ncovered by the 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":"Uninitialized memory exposed by `write::Decoder` on a corrupt legacy frame","id":"RUSTSEC-2026-0392","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.8.0"],"introduced":["0.4.22"],"last_affected":[],"package":"zstd","purl":"pkg:cargo/zstd","source":"RUSTSEC-2026-0392"}],"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-0392/"}