Skip to content
VulniPulse
Critical10.0Apache Software Foundation

CVE-2026-33453: Apache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code Execution

This Apache advisory covers CVE-2026-33453 in Apache Camel Camel-Coap.

Open the Apache advisory

Key facts

Vendor rating
Critical, CVSS 10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H · base score 10, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: changed. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
EPSS
9.18% chance of exploitation in the next 30 days (95th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Apache Camel 4.14.0 through 4.14.5; Apache Camel 4.18.0 before 4.18.1; Apache Camel 4.19.0
Fixed in
4.18.1
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationMessaging

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.

Text from the source record.

Affected versions
  • Apache Camel 4.14.0 through 4.14.5
  • Apache Camel 4.18.0 before 4.18.1
  • Apache Camel 4.19.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-33453

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply.
  • Users are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue.

CVE-2026-33453 in other vendors' advisories

Compare every advisory for CVE-2026-33453

Apache Software Foundation advisories, April 2026All Apache Software Foundation advisories

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)