Server-side Request Forgery (SSRF) Affecting org.apache.camel:camel-dns package, versions [,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-17892614
- published8 Jul 2026
- disclosed6 Jul 2026
- creditYu Bao
Introduced: 6 Jul 2026
CVE-2026-48205 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-dns to version 4.14.8, 4.18.3, 4.21.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the DnsConstants header handling in components/camel-dns/src/main/java/org/apache/camel/component/dns/DnsConstants.java and the DNS producers that consume those headers. An attacker can redirect DNS queries to an attacker-controlled resolver and probe internal hostnames by sending untrusted dns.server, dns.name, dns.domain, dns.type, dns.class, or term headers into a route that bridges HTTP input to a dns: producer. Because those header names are plain strings that do not use the Camel header namespace, they pass through the normal HttpHeaderFilterStrategy from inbound HTTP requests into the Exchange. In an unauthenticated bridge route, this lets a remote client influence the DNS server and lookup target, exposing internal network names and allowing poisoned DNS responses.