RUSTSEC-2026-0392None▾ SunlitUninitialized memory exposed by `write::Decoder` on a corrupt legacy frame
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
From 0.4.22 to 0.7.x, the writer behind zstd::stream::write::Decoder set
its output buffer's length to its full capacity before each decompression
call, then to the position the call reported, and only checked for an error
afterwards. When decompression fails inside a legacy (zstd v0.4 to v0.7)
frame, the bundled zstd library reports the output as fully written although
nothing was written, so stale heap memory, up to the buffer size (32 KiB by
default), was passed to the wrapped writer.
Legacy support is enabled by default, and a few bytes of corrupt legacy frame are enough. Whether this reaches an attacker depends on where the application sends the decompressed output.
From 0.8.0, the writer uses zstd-safe's buffers, and the same flaw there is covered by the zstd-safe advisory for it, fixed in zstd-safe 8.2.0.
zstd >= 0.4.22, < 0.8.0Upgrade to a patched release:
zstd 0.8.0Connected by shared product, vendor, weakness, or advisory.