A PoC/exploit has been discovered for vulnerability CVE-2026-48205 PT ID: PT-2026-55901 Vendor: Apache Software Foundation Product: Apache Camel DNS 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, http://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 http://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. References: • https://dbugs.ptsecurity.com/vulnerability/PT-2026-55901 • https://github.com/oscerd/cve-2026-48205 #dbugs_vuln
Post summary
A PoC/exploit for CVE‑2026‑48205—an SSRF vulnerability in Apache Camel DNS—has been discovered, detailing the attack vector and providing code references, though there is no evidence of active exploitation or patching.