Advisory

RUSTSEC-2026-0391

Also known as: None

Summary

Data from an abandoned stream leaks into the next stream on a reused context

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-10-16 12:00 UTC
Modified
2026-11-02 09:30 UTC

Affected packages and fixes

zstd

crates.io · All systems

Affected

  • introduced 0.13.2, fixed 0.13.4, introduced 0.14.0-0, fixed 0.14.3 (semver)

Fixed versions

0.13.4, 0.14.3

Fix

  • Fixed version 0.13.4
    cargo update -p zstd --precise 0.13.4
  • Fixed version 0.14.3
    cargo update -p zstd --precise 0.14.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences