VulnerabilityPublished 18 Sep 2026Updated 15 Oct 2026

CVE-2026-93488: Red Hat Build of Apache Camel 3.33.3.SP2 · Unthrottled Resource Allocation

Affects Red Hat Build of Apache Camel 3.33.3.SP2Source CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; 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 impacted component (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).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Sep 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 1 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.

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat Build of Apache Camel 3.33.3.SP2	Affected–	Fixed in–
Red HatRed Hat Build of Debezium 3.6	Affected–	Fixed in–
Red HatRed Hat build of Quarkus 3.27.5.SP2	Affected–	Fixed in–
Red HatRed Hat build of Quarkus 3.33.3.SP2	Affected–	Fixed in–
Red HatRed Hat AMQ Broker 7	Affected–	Fixed in–
Red HatRed Hat AMQ Clients	Affected–	Fixed in–

AI-suggested

Red Hat has published an official security advisory (RHSA-2026:69470) addressing this issue as part of an update to Red Hat build of Quarkus 3.27.5.SP2, which includes fixes for this and other vulnerabilities. Users should apply the available security update from Red Hat to remediate this vulnerability. Prior to applying this update, ensure all previous relevant errata are applied. Patch status is confirmed as fixed in the referenced advisory.

Description

CVE-2026-93488 is a denial of service vulnerability in the Netty component used by Red Hat Build of Apache Camel 3.33.3.SP2. The flaw arises because SpdySessionHandler accepts an unlimited number of concurrent remote-initiated streams due to the default localConcurrentStreams value being Integer.MAX_VALUE and no API to limit it. This allows a remote attacker to exhaust JVM heap and direct memory by opening many SPDY streams, leading to OutOfMemoryError and service disruption.

Impact

An unauthenticated remote attacker can cause a denial of service by exhausting JVM memory resources, resulting in application crashes or service unavailability. There is no impact on confidentiality or integrity reported.

Summary

The vulnerability in Netty's SpdySessionHandler allows a remote peer to open a SPDY connection and send an unlimited number of SYN_STREAM frames with FLAG_FIN=0. Since localConcurrentStreams defaults to Integer.MAX_VALUE and cannot be changed via an API, this results in unbounded heap and direct memory allocation. Consequently, this can cause the JVM to run out of memory, leading to a denial of service condition. This issue affects Red Hat Build of Apache Camel 3.33.3.SP2 as it bundles the vulnerable Netty version.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Oct 2026, 20:17 UTC

Technical details

References

Community reviews

Related threats