CyberSecBulletin
CVE-2026-93568NVD status: Awaiting Analysis

A flaw was found in Netty. A remote attacker could exploit this vulnerability by sending…

Published Updated By the CyberSecBulletin desk

CVE-2026-93568 is a high-severity improper input validation vulnerability in Red Hat Build of Apache Camel 3.33.3.SP2 from Red Hat, with a CVSS 3.1 base score of 7.5 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 1.08% chance of exploitation within 30 days, higher than 66% 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
NoneNo data is disclosed.
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:N/I:H/A:N. Scored by CNA (redhat.com).

Official description

A flaw was found in Netty. A remote attacker could exploit this vulnerability by sending specially crafted HTTP/2 or HTTP/3 Extended CONNECT requests. Netty's HTTP-object conversion path incorrectly processes these requests as regular HTTP/1.1 CONNECT requests, leading to a loss of critical protocol and path information. This misinterpretation can allow attackers to bypass security policies, such as routing or authorization logic, in applications that rely on Netty for HTTP/2 or HTTP/3 communication, resulting in integrity loss.

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

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

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 Improper Input Validation vulnerabilities

Spotted an error? Tell us.