CVE-2026-49086 camel vulnerability
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.
Quick answer
apache camel should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-49086 affects Apache Camel DAPR. Upgrade Apache Camel on the deployed branch to a fixed release (4.14.8, 4.18.3, 4.21.0) and review routes that expose this component to external or user-controlled messages. Affected ranges in the local NVD record are 4.12.0 through before 4.14.8; 4.15.0 through before 4.18.3; 4.19.0 through before 4.21.0.
- Inventory every service, integration route, container image, and build manifest that includes Apache Camel DAPR or transitive Camel modules related to DAPR.
- Compare each deployed Camel version with the affected ranges for CVE-2026-49086; treat 4.0.x-4.14.7, 4.15.x-4.18.2, and 4.19.x-4.20.x as needing an upgrade when the component is present.
- Upgrade to the fixed Camel release for the active branch: 4.14.8, 4.18.3, 4.21.0, or a later vendor-supported release.
- Rebuild application artifacts and container images from a clean dependency lockfile so no vulnerable Camel module remains through transitive dependencies.
- Harden exposed routes by filtering user-controlled Camel headers and component-specific control headers before data reaches Camel producers or internal route logic.
- Rotate credentials or integration tokens if logs, routing headers, backend endpoints, or message contents may have been exposed or redirected through the vulnerable route.
- Deploy first to staging, run regression tests for the impacted route, then promote to production with monitoring for routing errors, authorization failures, SSRF attempts, and unexpected message destinations.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm dependency output shows Apache Camel 4.14.8, 4.18.3, 4.21.0 or a later fixed release in every affected application.
- Run route-level tests that replay malicious or unexpected headers and verify they are removed, ignored, or rejected before reaching Camel internals.
- Check application logs after deployment for exceptions, leaked stack traces, SSRF indicators, unauthorized backend operations, or unexpected route destinations.
- Open the generated Fixnx page and confirm the canonical URL ends with camel-cve-2026-49086.
- Re-run sitemap validation and confirm camel-cve-2026-49086 appears once in sitemap.xml with the full CVE-2026-49086 suffix.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-49086?
apache camel should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.