CyberSecBulletin
CVE-2026-93569NVD status: Awaiting Analysis

Red Hat Build of Apache Camel 3.33.3.SP2: Inconsistent Interpretation of HTTP Requests

Published Updated By the CyberSecBulletin desk

CVE-2026-93569 is a high-severity inconsistent interpretation of HTTP requests vulnerability in Red Hat Build of Apache Camel 3.33.3.SP2 from Red Hat, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.42% chance of exploitation within 30 days, higher than 84% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Red Hat Build of Apache Camel 3.33.3.SP2 you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat Build of Apache Camel 3.33.3.SP2Not specified in the recordNot stated
Red HatRed Hat Build of Debezium 3.6Not specified in the recordNot stated
Red HatRed Hat build of Keycloak 26.4Not specified in the recordNot stated
Red HatRed Hat build of Keycloak 26.4.17Not specified in the recordNot stated
Red HatRed Hat build of Keycloak 26.6Not specified in the recordNot stated
Red HatRed Hat build of Keycloak 26.6.8Not specified in the recordNot stated
Red HatRed Hat build of Quarkus 3.27.5.SP2Not specified in the recordNot stated
Red HatRed Hat build of Quarkus 3.33.3.SP2Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8.1Not specified in the recordNot stated
Red HatRed Hat AMQ Broker 7Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4 for Quarkus 3Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel for Spring Boot 4Not specified in the recordNot stated
Red HatRed Hat build of Apicurio Registry 3Not specified in the recordNot stated
Red HatRed Hat Data Grid 8Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat Single Sign-On 7Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
LowSome restricted data can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N. Scored by CNA (redhat.com).

Official description

A flaw was found in Netty. A remote unauthenticated attacker can exploit a vulnerability in Netty's HTTP/1 to HTTP/2 conversion process. When an HTTP/1 request includes both an absolute-form request-target and a conflicting Host header, Netty incorrectly prioritizes the Host header for the HTTP/2 :authority field, discarding the original request-target authority. This inconsistency can allow an attacker to bypass security controls in Netty-based proxies or gateways, potentially leading to unauthorized access, cache poisoning, or misrouting of requests.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Inconsistent Interpretation of HTTP Requests

The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

How developers prevent this class of flaw

  • Use a web server that employs a strict HTTP parsing procedure, such as Apache.
  • Terminate the client session after each request.

More Inconsistent Interpretation of HTTP Requests vulnerabilities (CWE-444)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Red Hat Build of Apache Camel 3.33.3.SP2

All Red Hat Build of Apache Camel 3.33.3.SP2 vulnerabilities

Recent Inconsistent Interpretation of HTTP Requests vulnerabilities

Spotted an error? Tell us.