Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-48205 – Server-Side Request Forgery (SSRF) via DNS Header Injection – Apache Camel camel…

Be the first to know when new zero-days emerge:

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-dns producers read DNS operation parameters from Exchange message headers using constant names — dns.server, dns.name, dns.domain, dns.type, dns.class, and term — that do not carry the Camel/ prefix. Because HttpHeaderFilterStrategy only 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, or camel-netty-http) into a dns: producer. No authentication is required when the HTTP consumer is unauthenticated.
  • Attack vector: A remote, unauthenticated attacker sends an HTTP request with the dns.server header set to an attacker-controlled DNS server address. This causes the dig producer’s SimpleResolver to direct DNS queries to that server (DNS-based SSRF), allowing the attacker to observe queried names and inject poisoned DNS responses. By additionally setting dns.name or dns.domain headers, 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, and CamelDnsTerm, replacing the former dns.* and term names.
  • If immediate patching is not possible: Strip the dns.* and term headers from all untrusted HTTP ingress before reaching the dns: 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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge