Skip to main content
VulnerabilityPublished Updated

CVE-2026-33453: Apache Camel · Mass Assignment

Affects Apache CamelSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 10.0 Critical : upgrade to 4.18.1 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
9.1% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.18.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Apr 2026

  2. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Apache to 4.18.1.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache CamelAffected
  • >=4.14.0 <=4.14.5
  • >=4.18.0 <4.18.1
  • =4.19.0
Fixed in
  • 4.18.1
Mavenorg.apache.camel/camel-coappkg:maven/org.apache.camel/camel-coapOther threatsAffected
  • =4.14.0
  • =4.18.0
  • =4.19.0
Fixed in–
MavenApache Software Foundation/org.apache.camel:camel-coappkg:maven/Apache Software Foundation/org.apache.camel:camel-coapOther threatsAffected
  • >=4.14.0 <=4.14.5
  • >=4.18.0 <4.18.1
  • =4.19.0
Fixed in
  • 4.18.1

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

AI-suggested

A fix is available. Users should upgrade Apache Camel to version 4.18.1 or 4.19.0, which address this vulnerability. The vendor advisory from Red Hat confirms these versions as patched releases. Until upgrading, users should consider disabling or restricting access to the camel-coap component or applying network-level controls to limit UDP traffic to the CoAP port (5683). However, the primary and recommended mitigation is to apply the official patch by upgrading to the fixed versions.

Description

Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel Camel-Coap component. Apache Camel's camel-coap component is vulnerable to Camel message header injection, leading to remote code execution when routes forward CoAP requests to header-sensitive producers (e.g. camel-exec) The camel-coap component maps incoming CoAP request URI query parameters directly into Camel Exchange In message headers without applying any HeaderFilterStrategy. Specifically, CamelCoapResource.handleRequest() iterates over OptionSet.getUriQuery() and calls camelExchange.getIn().setHeader(...) for every query parameter. CoAPEndpoint extends DefaultEndpoint rather than DefaultHeaderFilterStrategyEndpoint, and CoAPComponent does not implement HeaderFilterStrategyComponent; the component contains no references to HeaderFilterStrategy at all. As a result, an unauthenticated attacker who can send a single CoAP UDP packet to a Camel route consuming from coap:// can inject arbitrary Camel internal headers (those prefixed with Camel*) into the Exchange. When the route delivers the message to a header-sensitive producer such as camel-exec, camel-sql, camel-bean, camel-file, or template components (camel-freemarker, camel-velocity), the injected headers can alter the producer's behavior. In the case of camel-exec, the CamelExecCommandExecutable and CamelExecCommandArgs headers override the executable and arguments configured on the endpoint, resulting in arbitrary OS command execution under the privileges of the Camel process. The producer's output is written back to the Exchange body and returned in the CoAP response payload by CamelCoapResource, giving the attacker an interactive RCE channel without any need for out-of-band exfiltration.                                                                                                                                                                         Exploitation prerequisites are minimal: a single unauthenticated UDP datagram to the CoAP port (default 5683). CoAP (RFC 7252) has no built-in authentication, and DTLS is optional and disabled by default. Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply. This issue affects Apache Camel: from 4.14.0 through 4.14.5, from 4.18.0 before 4.18.1, 4.19.0. Users are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue.

References

Community reviews

Loading reviews…