Quick answers
- Is CVE-2026-87795 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87795 being exploited in the wild.
- How severe is CVE-2026-87795?
- High severity, with a CVSS score of 8.2, published 9 September 2026.
- Which products and versions are affected?
- Luben Zstd-Jni before 1.5.7-14.
- Is there a fix for CVE-2026-87795?
- A patch was published on 2026-08-16: Fixed in version 1.5.7-14 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-87795 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-87795?
- Check whether you run Luben Zstd-Jni 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.
Technical details
The vulnerability is an out-of-bounds memory read in the ZstdDictCompress constructor, where offset and length parameters are not validated before use. An attacker can supply untrusted values to these parameters to read memory beyond intended boundaries into the compression dictionary. The attack vector is network or local, depending on how the application exposes the constructor (no specific authentication is mentioned as required). Successful exploitation can leak sensitive data from the JVM heap or trigger a crash; patches are available in version 1.5.7-14 and later.
Affected products
- Luben zstd-jni before 1.5.7-14
Timeline
- 2026-09-09: disclosed
- 2026-08-16: patched: Fixed in version 1.5.7-14