Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Informational severity, published 16 October 2026.

Which products and versions are affected?

zstd-safe (crates.io) SEMVER:introduced=4.1.0,fixed=8.2.0; Gyscos Zstd-Safe 4.1.0 to 8.1.x.

Is there a fix for This vulnerability?

Yes. zstd-safe (crates.io): upgrade to 8.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked with local access, in a software library.

Check whether you run zstd-safe (crates.io) or Gyscos Zstd-Safe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

zstd-safe use-after-free in CParameter::StableInBuffer

Severity: info · Published 2026-10-16

The zstd-safe Rust library, which provides safe bindings to the Zstandard compression library, contains a use-after-free vulnerability in its experimental StableInBuffer feature. When enabled, the underlying C library retains a pointer to input data from one call and reads it in subsequent operations, but safe Rust code may deallocate that memory between calls. An attacker could exploit this to read freed memory or cause a crash.

Technologies: zstd-safe (crates.io), Gyscos Zstd-Safe. Vendors: crates.io, Gyscos.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Informational severity, published 16 October 2026.
Which products and versions are affected?: zstd-safe (crates.io) SEMVER:introduced=4.1.0,fixed=8.2.0; Gyscos Zstd-Safe 4.1.0 to 8.1.x.
Is there a fix for This vulnerability?: Yes. zstd-safe (crates.io): upgrade to 8.2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked with local access, in a software library.
Am I affected?: Check whether you run zstd-safe (crates.io) or Gyscos Zstd-Safe at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

zstd-safe (crates.io): upgrade to 8.2.0 or later
```
cargo update -p zstd-safe
```

Technical details

The vulnerability exists in zstd_safe::CCtx::set_parameter when CParameter::StableInBuffer(true) is set. The C library keeps a pointer to the input buffer from a streaming call and accesses it in later calls (flush_stream, end_stream) that do not provide new input. Rust's InBuffer only borrows data for a single call, allowing safe code to deallocate it between calls; the freed memory may then be read during compression. The flaw affects all versions using the underlying zstd C library 1.5.4 or later.

Affected products

gyscos zstd-safe 4.1.0 to 8.1.x

Timeline

2026-10-16: disclosed
2026-10-26: advisory
2026-10-26: patched: Fixed in zstd-safe 8.2.0 by refusing to enable the parameter

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.