VulnerabilityPublished 11 Nov 2026

CVE-2026-122096: Uncontrolled Resource Consumption Vulnerability

Source GCVE Database

Compare

Authoritative record:CVE-2026-122096· High

Not known to be exploited · fixed in 9.1.0 : patch Apache DataSketches Java soon.

Data as of 11 Nov 2026, 16:52 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 9.1.0

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 11 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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-jghc-rj2j-x37x

What to do

Affected software

Product	Affected	Fixed in
Apache DataSketches Javaorg.apache.datasketches:datasketches-java	Affected <=9.0.0	Fixed in–
Mavenorg.apache.datasketches/datasketches-java`pkg:maven/org.apache.datasketches/datasketches-java`Other threats	Affected <=9.0.0	Fixed in–

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

AI-suggested

Upgrade Apache DataSketches Java to version 9.1.0 or later, where this vulnerability is fixed. Avoid deserializing sketches from untrusted sources if upgrading is not immediately possible.

Description

Apache DataSketches Java versions through 9.0.0 contain an uncontrolled resource consumption vulnerability in the sketch deserialization process. This flaw allows crafted inputs to cause excessive memory allocation leading to OutOfMemoryError or indefinite loops during deserialization or updates. Only applications deserializing sketches from untrusted sources are affected. The issue is fixed in version 9.1.0.

Impact

Applications deserializing sketches from untrusted sources may experience denial of service due to excessive memory consumption or infinite loops, potentially causing application crashes or unresponsiveness.

Summary

The vulnerability in Apache DataSketches Java involves deserializers that trust sizes and counts declared in serialized input without validation. Maliciously crafted inputs can cause the application to allocate excessive memory, resulting in OutOfMemoryError. Additionally, a crafted string passed to FrequentLongsSketch.getInstance(String) can cause deserialization or subsequent updates to loop indefinitely. This affects versions through 9.0.0 and is resolved in 9.1.0.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 16:52 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats