Skip to main content
VulnerabilityPublished

CVE-2026-49086: Apache Camel Dapr · Improper Input Validation

Affects Apache Camel DaprSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium · fixed in 4.21.0 : update Apache Camel Dapr when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.21.0, 4.18.3, 4.14.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade Apache to 4.21.0, 4.18.3 or 4.14.8.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Camel DaprAffected
  • >=4.19.0 <4.21.0
Fixed in
  • 4.21.0
Apache Software FoundationApache Camel DaprAffected
  • >=4.15.0 <4.18.3
Fixed in
  • 4.18.3
Apache Software FoundationApache Camel DaprAffected
  • >=4.12.0 <4.14.8
Fixed in
  • 4.14.8
MavenApache Software Foundation/org.apache.camel:camel-daprpkg:maven/Apache Software Foundation/org.apache.camel:camel-daprOther threatsAffected
  • >=4.12.0 <4.14.8
  • >=4.15.0 <4.18.3
  • >=4.19.0 <4.21.0
Fixed in
  • 4.14.8
  • 4.18.3
  • 4.21.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.21.0. Users should upgrade to one of these versions to remediate the vulnerability. If immediate upgrade is not possible, users should remove the CamelDaprPubSubName and CamelDaprTopic headers from the Exchange between the Dapr consumer and any Dapr producer in the route (e.g., using removeHeaders('CamelDaprPubSubName', 'CamelDaprTopic')). Additionally, restrict publishing permissions on the subscribed Dapr Pub/Sub topic to trusted producers only.

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.

References

Community reviews

Loading reviews…