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=0.0.0-0,fixed=8.2.0; Zstd-Rs Zstd-Safe before 8.2.0.

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 Zstd-Rs 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 multithreaded compression context

Severity: info · Published 2026-10-16

zstd-safe is a Rust wrapper for the Zstandard compression library that supports parallel compression using multiple worker threads. When a multithreaded compression frame is left incomplete, operations that modify the compression context (such as changing the dictionary or the number of worker threads) can cause the library to access memory that has already been freed, potentially leading to memory corruption or crashes.

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

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=0.0.0-0,fixed=8.2.0; Zstd-Rs Zstd-Safe before 8.2.0.
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 Zstd-Rs 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

A use-after-free vulnerability occurs when multithreaded compression frames (enabled via zstdmt feature or CParameter::NbWorkers) are not fully completed before calling certain context-modification functions. Worker threads may still be using the old dictionary or job table after these functions free or resize them. The vulnerable functions are load_dictionary, ref_cdict, ref_prefix, disable_dictionary, init, reset, and set_parameter. The fix adds wait_for_workers() to ensure all outstanding worker jobs complete before allowing context modifications.

Affected products

zstd-rs zstd-safe before 8.2.0

Timeline

2026-10-16: disclosed
2026-10-26: advisory

References

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