VulnerabilityPublished 12 Sep 2026Updated 14 Sep 2026

CVE-2026-90560: luben zstd-jni · Out-of-bounds Read

Affects luben zstd-jniSource CVE Database V5

Not known to be exploited · CVSS 8.8 High : upgrade to 1.5.7-14 soon.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 4.0 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.5.7-14

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-392q-wrgq-6wmj

What to do

Upgrade zstd-jni and luben/zstd-jni to 1.5.7-14.

Affected software

Product	Affected	Fixed in
lubenzstd-jni	Affected >=1.2.0 <1.5.7-14	Fixed in 1.5.7-14
Mavenluben/zstd-jni`pkg:maven/luben/zstd-jni`Other threats	Affected >=1.2.0 <1.5.7-14	Fixed in 1.5.7-14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor for an official fix or update to zstd-jni beyond version 1.5.7-13. If you cannot patch yet, avoid processing untrusted input with vulnerable versions to mitigate risk.

Description

An out-of-bounds read vulnerability exists in the ZstdDictDecompress constructor of zstd-jni versions 1.2.0 through 1.5.7-13. This occurs because the offset and length parameters are not validated against the dictionary array bounds, allowing attackers to read memory beyond the intended array. This can potentially cause the Java Virtual Machine (JVM) to terminate unexpectedly.

Impact

Successful exploitation allows an attacker to cause an out-of-bounds read, potentially leading to JVM termination and denial of service. There is no indication of code execution or data disclosure beyond memory read. The impact is primarily on availability due to JVM crashes.

Summary

The vulnerability CVE-2026-90560 affects zstd-jni versions from 1.2.0 up to but not including 1.5.7-14. The issue is an out-of-bounds read in the ZstdDictDecompress constructor due to lack of validation of offset and length arguments against the dictionary array bounds. An attacker can exploit this by supplying arbitrary offset or length values, leading to reading memory past the end of the supplied array, which may cause JVM termination. The CVSS 4.0 base score is 8.8, indicating a high severity vulnerability with network attack vector, low complexity, no privileges or user interaction required, and high impact on availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2026, 23:15 UTC

Technical details

References

Community reviews

Related threats