JVM termination via unchecked dictionary bounds
Published Sep 12, 2026 · Updated Sep 12, 2026
Out-of-bounds read in Luben zstd-jni 1.2.0 through 1.5.7-13 allows attackers to terminate the JVM via crafted dictionary bounds. The ZstdDictDecompress byte-array constructor passes offset and length to native initialization without checking them against the supplied array. Reachability requires a consuming application to pass attacker-controlled constructor arguments; the resulting read crosses the array boundary and can crash the JVM.
Summary
What happened
Out-of-bounds read in Luben zstd-jni 1.2.0 through 1.5.7-13 allows attackers to terminate the JVM via crafted dictionary bounds. The ZstdDictDecompress byte-array constructor passes offset and length to native initialization without checking them against the supplied array. Reachability requires a consuming application to pass attacker-controlled constructor arguments; the resulting read crosses the array boundary and can crash the JVM.
The record
- CVE
- CVE-2026-90560
- Published
- Sep 12, 2026
- Updated
- Sep 12, 2026
- Vendor
- Luben
- Product
- zstd-jni
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 12, 2026CVE publishedPublication date reported by the CVE source.
- Sep 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.0 <1.5.7-14
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo