EUVD-2026-41842
GHSA-583r-f84w-33g7
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Network publish access required (AV:N, PR:L); scope changes as messages cross Dapr component boundaries (S:C); impact is redirection and exfiltration, not code execution (C:L/I:L/A:N).
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
4Blast Radius
ecosystem impact- 3 maven packages depend on org.apache.camel:camel-dapr (2 direct, 1 indirect)
Ecosystem-wide dependent count for version 4.12.0.
Description PRE-NVD
Articles & Coverage 4
AnalysisAI
Routing header injection in Apache Camel's camel-dapr component allows any actor with publish access to a subscribed Dapr Pub/Sub topic to redirect or exfiltrate re-published messages to an arbitrary Dapr Pub/Sub component and topic. The flaw exists in routes that both consume and republish via Dapr - specifically, DaprPubSubConsumer blindly copies attacker-controlled CloudEvent fields (pub/sub-name and topic) into producer-direction routing headers (CamelDaprPubSubName and CamelDaprTopic), which DaprConfigurationOptionsProxy then prefers over the route's configured endpoint destination. No public exploit code or CISA KEV listing exists at time of analysis, but exploitation is mechanically straightforward for any publisher on the subscribed topic.
Technical ContextAI
Apache Camel is a widely deployed open-source integration framework implementing Enterprise Integration Patterns (EIPs). The camel-dapr component (org.apache.camel:camel-dapr) bridges Camel routes with Dapr - the Distributed Application Runtime - enabling consumption and production of CloudEvents over Dapr's Pub/Sub API. The root cause is a confused-deputy flaw (CWE-441) compounded by improper input validation (CWE-20): DaprPubSubConsumer incorrectly promoted two sender-controlled CloudEvent fields - the pub/sub component name and topic - into Camel Exchange headers that are semantically meant for producer-side routing (CamelDaprPubSubName and CamelDaprTopic). Because DaprConfigurationOptionsProxy gives these headers priority over the statically configured endpoint URI when the route republishes, an attacker who controls the inbound CloudEvent payload can override the route author's intended destination. The fix (GitHub PR #23886, committed to main and backported) stops DaprPubSubConsumer from setting these headers at all, and adds a DaprHeaderFilterStrategy to formalize header handling for future consistency. The CloudEvent format exposes a fixed closed set of fields rather than an arbitrary sender-controlled header map, which is why the confused-deputy path was possible - the component trusted field values from an untrusted sender.
RemediationAI
The primary fix is to upgrade camel-dapr to a patched release: 4.14.8 for deployments on the 4.14.x LTS stream, 4.18.3 for those on the 4.18.x stream, or 4.21.0 for those on the latest stream. All three releases were announced by the Apache Camel community in early July 2026. The fix commits are confirmed in the upstream repository (GitHub PR #23886, main commit 72d13bd13fb5960ea1b367a2e379f017c1720c5c; 4.18.x backport commit 86276a2ccc2cf8b09d7efeb38d9770845c4e1bea; 4.14.x backport commit c6fc9bb21670e5c65ea14df0f3f29baef78c2028). For deployments that cannot upgrade immediately, two compensating controls should be applied together: first, add an explicit removeHeaders('CamelDaprPubSubName', 'CamelDaprTopic') step between the Dapr consumer and any Dapr producer in the route - this strips the attacker-controlled headers before the producer reads them, preventing routing override (trade-off: this requires modifying every affected route definition and must be re-applied if routes are regenerated); second, restrict who can publish to the subscribed Dapr Pub/Sub topic to only trusted, authenticated producers at the broker level - this reduces the attacker pool but does not eliminate the header-injection path if the topic is shared. Full advisory: https://camel.apache.org/security/CVE-2026-49086.html.
Bypass/Injection vulnerability in Apache Camel components under particular conditions.10.0 through <= 4.10.1, from 4.8.0
The XSLT component in Apache Camel before 2.11.4 and 2.12.x before 2.12.3 allows remote attackers to read arbitrary file
Apache Camel's Jackson and JacksonXML unmarshalling operation are vulnerable to Remote Code Execution attacks. Rated cri
The XSLT component in Apache Camel 2.11.x before 2.11.4, 2.12.x before 2.12.3, and possibly earlier versions allows remo
Cross-realm token acceptance bypass in Apache Camel Keycloak security policy. The KeycloakSecurityPolicy fails to proper
Deserialization of Untrusted Data vulnerability in Apache Camel LevelDB component. The Camel-LevelDB DefaultLevelDBSeria
Unsafe Java deserialization in the Apache Camel camel-mina component (versions 3.0.0 through 4.14.5, 4.15.0 through 4.18
Apache Camel's File is vulnerable to directory traversal. Rated high severity (CVSS 7.5), this vulnerability is remotely
The camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-se
The camel-xstream component in Apache Camel before 2.15.5 and 2.16.x before 2.16.1 allow remote attackers to execute arb
The camel-hessian component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-s
Apache Camel before 2.9.7, 2.10.0 before 2.10.7, 2.11.0 before 2.11.2, and 2.12.0 allows remote attackers to execute arb
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today