CVE-2026-49086 Apache Camel-Dapr: The Dapr Pub/Sub consumer copied the inbound CloudEvent's pub/sub-name and topic into producer-direction routing headers

Medium 6.5 Published Updated

An attacker publishing to a subscribed topic can redirect messages to arbitrary destinations by manipulating CloudEvent headers, bypassing routing controls.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-49086?

CVE-2026-49086 is a medium-severity vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Improper Input Validation, Unintended Proxy or Intermediary ('Confused Deputy') vulnerability in Apache Camel DAPR component.

The camel-dapr Dapr Pub/Sub consumer (DaprPubSubConsumer) copied two fields from each inbound CloudEvent - its Pub/Sub component name and its topic - into the CamelDaprPubSubName and CamelDaprTopic Exchange headers. These two headers are producer-direction routing headers: when the route republishes through a Dapr producer, DaprConfigurationOptionsProxy reads them back and prefers them over the destination configured on the endpoint. As a result, in a route that consumes from one Dapr Pub/Sub topic and republishes to another (for example from('dapr-pubsub:p:t').to('dapr-pubsub:p:other')), an actor able to publish a message to the subscribed topic could set the CloudEvent's pub/sub-name and topic to values of their choosing and cause the re-published message to be delivered to an arbitrary Dapr Pub/Sub component and topic instead of the configured destination - redirecting or exfiltrating the message and bypassing the route's intended routing and any topic-level access controls in the underlying broker. Exploitation requires the ability to publish to the topic the route subscribes to; no other authentication or user interaction is needed. This issue affects Apache Camel: from 4.12.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.

Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, remove the CamelDaprPubSubName and CamelDaprTopic headers from the Exchange between the Dapr consumer and any Dapr producer in the route (for example removeHeaders('CamelDaprPubSubName', 'CamelDaprTopic')), and restrict who can publish to the subscribed Dapr Pub/Sub topic so that only trusted producers can send to it.

Weakness: CWE-441, CWE-20

Which versions are affected by CVE-2026-49086?

6 open source packages ship an affected version, including org.apache.camel:camel-dapr. It affects 1 product.

PackageAffectedFixed in
org.apache.camel:camel-dapr MavenFrom 4.12.04.14.8
org.apache.camel:camel-dapr MavenFrom 4.12.04.14.8
org.apache.camel:camel-dapr MavenFrom 4.15.04.18.3
org.apache.camel:camel-dapr MavenFrom 4.15.04.18.3
org.apache.camel:camel-dapr MavenFrom 4.19.04.21.0
org.apache.camel:camel-dapr MavenFrom 4.19.04.21.0

Products include Apache Camel.

How do I fix CVE-2026-49086?

Upgrade org.apache.camel:camel-dapr to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0.

Is CVE-2026-49086 being exploited?

There is no known exploitation of CVE-2026-49086 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

All Apache Camel vulnerabilities

Sources

Also known as GHSA-583r-f84w-33g7.

Is CVE-2026-49086 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free