Summary
CVE-2026-48205 is a critical Server-Side Request Forgery (SSRF) and Improper Input Validation vulnerability (CWE-918, CWE-20) in the Apache Camel DNS component (camel-dns), rated CVSS 9.1. In Camel routes that bridge an HTTP consumer into a dns: producer, an unauthenticated remote attacker can manipulate DNS operation parameters by injecting specially crafted HTTP headers, enabling redirection of DNS queries to an attacker-controlled server and enumeration of internal hostnames.
Technical details
- Root cause: The
camel-dnsproducers read DNS operation parameters from Exchange message headers using constant names —dns.server,dns.name,dns.domain,dns.type,dns.class, andterm— that do not carry theCamel/prefix. BecauseHttpHeaderFilterStrategyonly blocks headers within the Camel namespace at the HTTP boundary, these headers pass through unfiltered from any inbound HTTP request directly into the Exchange. - Trigger condition: Exploitation requires a Camel route that bridges an HTTP consumer (such as
platform-http,camel-servlet,camel-jetty,camel-undertow, orcamel-netty-http) into adns:producer. No authentication is required when the HTTP consumer is unauthenticated. - Attack vector: A remote, unauthenticated attacker sends an HTTP request with the
dns.serverheader set to an attacker-controlled DNS server address. This causes thedigproducer’sSimpleResolverto direct DNS queries to that server (DNS-based SSRF), allowing the attacker to observe queried names and inject poisoned DNS responses. By additionally settingdns.nameordns.domainheaders, the attacker can resolve arbitrary internal hostnames, disclosing the existence of internal infrastructure. - Impact: Confidentiality and Integrity are both rated HIGH. The attacker can intercept sensitive DNS queries, return fraudulent DNS records, and conduct internal network reconnaissance — all without credentials.
Affected software
- Apache Camel 4.0.0 through 4.14.7
- Apache Camel 4.15.0 through 4.18.2
- Apache Camel 4.19.0 through 4.20.x
Severity
CVSS v3.1 base score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Mitigation and recommended actions
- Immediate — patch: Upgrade to Apache Camel 4.21.0. Users on the 4.14.x LTS stream should upgrade to 4.14.8; users on the 4.18.x stream should upgrade to 4.18.3.
- Post-upgrade route changes required: After upgrading, any routes that reference DNS operation headers by raw names must be updated to use the new Camel-prefixed constants:
CamelDnsServer,CamelDnsName,CamelDnsDomain,CamelDnsType,CamelDnsClass, andCamelDnsTerm, replacing the formerdns.*andtermnames. - If immediate patching is not possible: Strip the
dns.*andtermheaders from all untrusted HTTP ingress before reaching thedns:producer, and set DNS server and lookup parameters exclusively from a trusted, internal source within the route.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

