dbcve.org
CamelApplication · Apache

CVE-2026-49086

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-06
Fix available
A fix is available. Upgrade to 4.14.8 / 4.18.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Apache Camel's DAPR component, the DaprPubSubConsumer copies inbound CloudEvent pub/sub name and topic fields into CamelDaprPubSubName and CamelDaprTopic exchange headers. When the route subsequently republishes through a Dapr producer, DaprConfigurationOptionsProxy reads these headers and uses them instead of the configured endpoint destination. An attacker who can publish to the subscribed topic can inject arbitrary pub/sub names and topics to redirect messages to unintended destinations.

MitigationUpgrade to Apache Camel 4.21.0 (or 4.18.3/4.14.8 for LTS streams), or insert removeHeaders('CamelDaprPubSubName','CamelDaprTopic') between the Dapr consumer and producer in affected routes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CamelApplication
Affected:>= 4.12.0, < 4.14.8>= 4.15.0, < 4.18.3>= 4.19.0, < 4.21.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Camel version
    Run 'mvn org.apache.camel:camel-maven-plugin:4.x.x:version' or check the camel-core JAR manifest, or inspect the classpath for camel-core version
    Affected if version falls within >= 4.12.0, < 4.14.8 OR >= 4.15.0, < 4.18.3 OR >= 4.19.0, < 4.21.0
  2. Verify DAPR component is in use
    Search project dependencies for 'camel-dapr' or inspect runtime classpath for org.apache.camel.component.dapr.* classes
    Affected if camel-dapr dependency is present in the project
  3. Identify routes with Dapr consumer to producer chain
    Review Camel route definitions (Java DSL, XML, or YAML) for routes that use 'dapr:' consumers (dapr:pubsubname/topic) followed by a Dapr producer endpoint
    Affected if a route consumes from a Dapr pub/sub topic and then sends to a Dapr producer endpoint without removing headers in between
  4. Inspect exchange headers for Dapr fields
    Add a wiretap or logging step in the route to inspect exchange headers, specifically CamelDaprPubSubName and CamelDaprTopic, after the Dapr consumer and before the producer
    Affected if these headers are present and propagate from consumer to producer in the route flow
  5. Check for header sanitization
    Review route code for removeHeaders('CamelDaprPubSubName','CamelDaprTopic') or equivalent header stripping logic between the Dapr consumer and any subsequent Dapr producer
    Affected if no header removal occurs and a Dapr consumer is followed by a Dapr producer in the same route

User is affected if running a vulnerable Camel version with camel-dapr in use and a route that chains a Dapr pub/sub consumer directly to a Dapr producer without stripping the CamelDaprPubSubName and CamelDaprTopic headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.8 / 4.18.3 / 4.21.0 or later
Fixed in 4.14.84.18.34.21.0
Interim mitigation

Upgrade to Apache Camel 4.21.0 (or 4.18.3/4.14.8 for LTS streams), or insert removeHeaders('CamelDaprPubSubName','CamelDaprTopic') between the Dapr consumer and producer in affected routes.

Recommended fix High confidence

4.21.0 (or 4.14.8 for 4.14.x LTS, or 4.18.3 for 4.18.x)

  1. Identify the current Apache Camel version in use by checking the project dependencies or pom.xml
  2. Determine which release stream the current version belongs to (4.12.x-4.14.x, 4.15.x-4.18.x, or 4.19.x-4.20.x)
  3. For 4.14.x LTS stream: upgrade to version 4.14.8
  4. For 4.15.x-4.18.x stream: upgrade to version 4.18.3
  5. For 4.19.x-4.20.x stream: upgrade to version 4.21.0
  6. Verify the upgrade by rebuilding and testing the application, specifically testing routes that use dapr-pubsub consumers and producers
  7. Confirm that the CamelDaprPubSubName and CamelDaprTopic headers are no longer being used to override the configured destination

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Camel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49086 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data