CVE-2026-48205 camel vulnerability
Improper Input Validation, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel DNS component. The camel-dns producers read DNS operation parameters - the resolver to query, the name or domain to look up, the record type and class, and the search term - from Exchange message headers whose constant values (DnsConstants.DNS_SERVER, DNS_NAME, DNS_DOMAIN, DNS_TYPE, DNS_CLASS, TERM) were the plain strings dns.server, dns.name, dns.domain, dns.type, dns.class and term. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a dns: producer, any HTTP client could therefore set the dns.server header to make the dig producer build a SimpleResolver pointing at an attacker-controlled DNS server - a server-side request forgery via DNS, through which the attacker observes the queried name and can return poisoned responses - and set the dns.name / dns.domain headers to resolve arbitrary internal hostnames, disclosing whether they exist (internal network reconnaissance). No credentials are required when the bridging consumer is unauthenticated. This issue affects Apache Camel: from 4.0.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. After upgrading, routes that drive DNS operations via the raw header names must use CamelDnsServer / CamelDnsName / CamelDnsDomain / CamelDnsType / CamelDnsClass / CamelDnsTerm instead of the dns.* / term names. For deployments that cannot upgrade immediately, strip the dns.* and term headers from any untrusted ingress before the dns: producer, and set the DNS server and lookup parameters from a trusted source in the route.
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-48205 affects Apache Camel DNS. 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.0.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 DNS or transitive Camel modules related to DNS.
- Compare each deployed Camel version with the affected ranges for CVE-2026-48205; 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-48205.
- Re-run sitemap validation and confirm camel-cve-2026-48205 appears once in sitemap.xml with the full CVE-2026-48205 suffix.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-48205?
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.