Quick answers
- Is CVE-2026-89045 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89045 being exploited in the wild.
- How severe is CVE-2026-89045?
- Medium severity, with a CVSS score of 4, published 10 September 2026.
- Which products and versions are affected?
- Luben Zstd-Jni 1.4.8-4 through 1.5.7-13.
- Is there a fix for CVE-2026-89045?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-89045 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-89045?
- 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 input validation flaw in the ZstdInputStreamNoFinalizer.read() method, which does not properly check for negative length parameters. When a negative length value is passed to the read() method, it enters an infinite loop while holding the stream's monitor lock, preventing other threads from accessing the stream. The affected versions are 1.4.8-4 through 1.5.7-13. This is a local or adjacent network attack that requires the attacker to be able to invoke the vulnerable method with a malicious parameter; no authentication bypass or remote exploitation is involved. A patch is available in version 1.5.7-14 and later.
Affected products
- Luben zstd-jni 1.4.8-4 through 1.5.7-13
Timeline
- 2026-09-10: disclosed
- 2026-08-16: other: Version 1.5.7-14 released with fix (prior to disclosure)