cve.bz

CVE-2026-33453 apache camel

10.0 criticalEPSS 9.2%Fix available

Critical (10.0) in apache camel. EPSS 9.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-coap 4.14.6, 4.18.1.

On this page
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.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
9.2% (unchanged from 9.2% a week ago; 7.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 95th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-04-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.apache.camel:camel-coap (Maven): fixed in 4.14.6, 4.18.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-33453 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33453?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33453?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33453 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-33453

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-33453](https://cve.bz/cve/badge/CVE-2026-33453.svg)](https://cve.bz/cve/CVE-2026-33453)

HTML:

<a href="https://cve.bz/cve/CVE-2026-33453"><img src="https://cve.bz/cve/badge/CVE-2026-33453.svg" alt="CVE-2026-33453"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.14.0 through 4.14.5
Apache Software Foundation Apache Camelfrom 4.18.0 before 4.18.1
Apache Software Foundation Apache Camel4.19.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-695c-x5gc-94gjMavenorg.apache.camel:camel-coap>=4.14.0 <4.14.64.14.6
GHSA-695c-x5gc-94gjMavenorg.apache.camel:camel-coap>=4.18.0 <4.18.14.18.1

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14camel-coapFixed 2026-05-14RHSA-2026:17668
Red Hat Fuse 7apache-camelNot affected
Red Hat Fuse 7apache-camel-k-runtimeNot affected
Red Hat Fuse 7camel-coapNot affected
Red Hat Fuse 7camel-coap-starterNot affected
Red Hat JBoss Enterprise Application Platform 8camel-coapNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-coapNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-33453.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-33453 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-33453: Apache Camel camel-coap header injection to RCE via camel-exec
  • dinosn/CVE-2026-33453 Harbor Check: matches CVE 0 stars, Python, created
    Apache Camel 4.18.0 — CVE Security Assessment: 3 critical vulnerabilities with working PoC exploits (CVE-2026-33453, CVE-2026-40473, CVE-20…

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

References

Check your stackJSON