Zstd: Data from an abandoned stream leaks into the next stream on a reused context
Affects zstdSource GCVE Database
Rated by Threat Radar
- Patch
- Available – fixed in 0.14.3
Data as of 26 Oct 2026, 16:13 UTC
What to do
Upgrade zstd to 0.14.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iozstdpkg:cargo/zstdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The `with_context` constructors of the stream encoders and decoders used the borrowed context as it was. When a stream was abandoned on a context, for example an encoder dropped before `finish()` after an error, whatever it left there was carried into the next stream: the input buffered by the previous encoder (up to 128 KiB, or all of it with `zstdmt`) became the start of the next frame, and a decoder returned undelivered output of the previous stream. An application reusing one context for data that must stay separate, such as different users' requests, could disclose one user's plaintext to another. Whoever supplies the data can cause the abandonment with invalid input. The flaw was corrected by resetting the context's session in `with_context`.