Dapr Pub/Sub headers can influence internal routing
Medium (6.5)Published
CVE-2026-49086 is an Apache Camel Dapr confused-deputy vulnerability that lets publishers influence internal routing.
- Affected
- Apache Camel Dapr 4.12.0–4.14.7, 4.15.0–4.18.2, and 4.19.0–4.20.x
- Attack requirements
- Permission to publish to a Dapr Pub/Sub topic consumed and then republished by a Camel route
Impact
A publisher can redirect a republished message to an arbitrary Dapr Pub/Sub component and topic. This can bypass the route's configured destination and the topic-level access boundaries expected by the application.
Technical detail
- DaprPubSubConsumer copied the inbound CloudEvent pub/sub name and topic into CamelDaprPubSubName and CamelDaprTopic exchange headers.
- Those headers control producer-side routing, and DaprConfigurationOptionsProxy preferred them over the destination configured on the endpoint.
- A message publisher could therefore supply routing values that were later trusted when the route republished the exchange.
Remediation
- Upgrade to Apache Camel 4.14.8, 4.18.3, or 4.21.0 and later, according to the release line in use.
- For a temporary mitigation, remove CamelDaprPubSubName and CamelDaprTopic between the Dapr consumer and producer.
- Restrict publishing access to the subscribed topic to trusted producers.