ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0344

Decompression bomb in : a tiny input can exhaust memory (OOM)

Published Oct 11, 2026 · catalog updated Oct 13, 2026 · RustSec Rust

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0344. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
crates.io ruzstd

A crafted input under 128 KB can force to allocate several gigabytes at once, crashing the process with an out-of-memory condition. Since is a decoder for untrusted input, a single small file is enough to take down anything decoding it. The compressed size of a block was capped at 128 KB, but a compressed block's **decompressed** size was never checked against (RFC 8878). In the output was built with no running bound and no flush between blocks, so one block could expand to gigabytes — bypassing both the configured window-size limit and the block-by-block streaming that would otherwise release memory. (A related counter overflow on such a block caused an additional panic.) This is a denial of service only; memory access stays in bounds (no corruption, no RCE). is also built as a dependency of the Rust standard library via ; in the toolchain it is used only to load zstd-compressed debug symbols, so the toolchain-side impact is limited. **Fixed in 0.9.1** (commit ), which enforces the per-block output bound. Upgrade to .

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io ruzstd0.0.0-0 → 0.9.1

How to fix RUSTSEC-2026-0344

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2026-0344. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.0.0-0 → 0.9.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 11, 2026 · Catalog

    Detected

    A crafted input under 128 KB can force to allocate several gigabytes at once, crashing the process with an out-of-memory condition. Since is a decoder for untrusted input, a single small file is enough to take down anything decoding it. The compressed size of a block was capped at 128 KB, but a compressed block's **decompressed** size was never checked against (RFC 8878). In the output was built w

  2. Oct 13, 2026 · Catalog

    Fix available

    crates.io ruzstd 0.0.0-0 → 0.9.1

  3. Oct 13, 2026 · Catalog

    Updated

    A crafted input under 128 KB can force to allocate several gigabytes at once, crashing the process with an out-of-memory condition. Since is a decoder for untrusted input, a single small file is enough to take down anything decoding it. The compressed size of a block was capped at 128 KB, but a compressed block's **decompressed** size was never checked against (RFC 8878). In the output was built w

Sources

  • OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0344

    Decompression bomb in : a tiny input can exhaust memory (OOM)

    osv.dev
  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0344

    A crafted input under 128 KB can force to allocate several gigabytes at once, crashing the process with an out-of-memory condition. Since is a decoder for untrusted input, a single small file is enough to take down anything decoding it. The compressed size of a block was capped a

    crates.io

References

Freshness

Last verified in this catalog Oct 13, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.