Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · RUSTSEC-2026-0392

Uninitialized memory exposed by `write::Decoder` on a corrupt legacy frame

No CVSS score

Published by OSV at 16 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
zstdcrates.io>=0.4.22, <0.8.00.8.0
Identifiers
RUSTSEC-2026-0392
Published
16 Oct 2026
Updated
26 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of the zstd crate from 0.4.22 up to but not including 0.8.0 are affected. When `zstd::stream::write::Decoder` receives a corrupt legacy (zstd v0.4 to v0.7) frame, which is enabled by default, decompression fails but the output buffer is still passed to the wrapped writer, exposing up to 32 KiB of stale heap memory. Whether this reaches an attacker depends on where the application sends the output. Upgrade to zstd 0.8.0 or later.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.