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 over the network.
- 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
An integer overflow in the `train_from_buffer` function fails to detect when the sum of sample sizes overflows in release builds (where overflow checks are disabled). An attacker providing crafted sample sizes (e.g., totaling 2^64 plus the buffer length) can bypass the bounds check and cause the trainer to read past the end of the buffer. The vulnerability requires untrusted sample size input and is fixed by adding explicit overflow checks during summation.
Affected products
- zstd-rs zstd-safe before 8.2.0
Timeline
- 2026-10-16: disclosed
- 2026-10-26: advisory
- 2026-10-26: patched