CVE-2026-33453
CVE-2026-33453 is a critical-severity vulnerability in Apache Software Foundation Apache Camel (CVSS 3.1 base score 10.0), classified as CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes). It is not in the CISA Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment rates its exploitation as none. As of 2026-11-22, EPSS estimates a 9.2% probability of exploitation in the next 30 days, in the 95th percentile of scored CVEs.
Updated
- CVSS 3.1
- 10.0 CRITICAL
- EPSS
- 9.2% (95th pct)
- CISA KEV
- Not listed
- Published
- 2026-04-27
- Weakness
- CWE-915
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.
Key Findings
as of 2026-11-22- Its current EPSS score (9.2%) is higher than that of 23% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesIf CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 3 days and forensic triage on other assets.
Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable yes, technical impact total, 2026-04-27).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
If CISA adds the CVE to the KEV catalog, the timeline shortens.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| Apache Software Foundation | Apache Software Foundation Apache Camel | 4.14.0 to 4.14.5 4.18.0 to <4.18.1 4.19.0 |
References
2 linksVendor advisories
Other references
Record Details
- Published
- 2026-04-27
- Last updated
- 2026-07-15
- Assigner (CNA)
- apache
- Credited to
- Hyunwoo Kim (@v4bel)
More from Apache
Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering
Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Apache Struts Remote Code Execution Vulnerability
mod_proxy SSRF
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.