CVE-2026-48205: Apache Camel DNS SSRF
This Apache advisory covers CVE-2026-48205 in Apache Camel DNS.
- CVE-2026-48205
Key facts
- Vendor rating
- Critical, CVSS 9.1
- CISA KEV
- Not listed (catalogue checked )
- Affected
- 4.0.0 through 4.14.8; 4.15.0 through 4.18.3; 4.19.0 through 4.21.0.
- Fixed in
- 4.21.0, 4.14.8, 4.18.3
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
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.
Text from the source record.
- 4.0.0 through 4.14.8
- 4.15.0 through 4.18.3
- 4.19.0 through 4.21.0.
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-48205
Upgrade to a fixed release named by Apache:
- 4.21.0
- 4.14.8
- 4.18.3
Vendor guidance
- 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, 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.
More Apache Software Foundation advisories
CVE-2026-86336Nov 10, 2026Apache TomEE running on JDK 21 or later skips EJB method authorization checksCVE-2026-86531Nov 10, 2026The embedded OpenEJB HTTP server does not limit the size of incoming request bodiesCVE-2026-87758Nov 10, 2026The remote EJB client does not verifyCVE-2026-97849Nov 10, 2026The embedded Derby network service ignores its configured bind address and listens on allCVE-2026-97867Nov 10, 2026The EJBd remote protocol returns datasource connection details, including databaseCVE-2026-97870Nov 10, 2026When Hessian remoting endpoints are served by the embedded HTTP server, configured
Apache Software Foundation advisories, July 2026All Apache Software Foundation advisories
Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.
See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
