---
title: "CVE-2026-48205: Apache Camel DNS Has Improper Input Validation, Leading to Server-Side Request Forgery (SSRF)"
url: https://erroneo.us/security/cve/CVE-2026-48205/
description: "CVE-2026-48205 (org.apache.camel:camel-dns (Maven)): Improper Input Validation, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel DNS…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-07-06
date_modified: 2026-07-24
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-48205"
kev: false
cvss: 9.1
epss: 0.006
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-48205: Apache Camel DNS Has Improper Input Validation, Leading to Server-Side Request Forgery (SSRF)

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.6% , percentile 48: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 48% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes org.apache.camel:camel-dns (Maven) >= 4.0.0, < 4.14.8, fixed in 4.14.8 ; org.apache.camel:camel-dns (Maven) >= 4.15.0, < 4.18.3, fixed in 4.18.3 ; org.apache.camel:camel-dns (Maven) >= 4.19.0, < 4.21.0, fixed in 4.21.0 . Check your lockfile, including transitive dependencies.

## What it is

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.DNSSERVER, DNSNAME, DNSDOMAIN, DNSTYPE, DNSCLASS, 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. 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. 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. After upgrading, routes that drive DNS operations via the raw header names must use CamelDnsServer / CamelDnsName / CamelDnsDomain / CamelDnsType / CamelDnsClass / CamelDnsTerm instead of the dns. / term names. 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.

## Affected packages

- Maven `org.apache.camel:camel-dns` >= 4.0.0, < 4.14.8 → fixed: 4.14.8
- Maven `org.apache.camel:camel-dns` >= 4.15.0, < 4.18.3 → fixed: 4.18.3
- Maven `org.apache.camel:camel-dns` >= 4.19.0, < 4.21.0 → fixed: 4.21.0

## Affected products (CVE record)

- Apache Software Foundation Apache Camel DNS: 4.0.0 < 4.14.8, 4.15.0 < 4.18.3, 4.19.0 < 4.21.0

## Severity

- CISA-ADP CVSS 3.1: 9.1 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`
- GitHub CVSS 3.1: 9.1 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.60% probability of exploitation activity in the next 30 days; percentile 48.

## Sources

- [camel.apache.org](https://camel.apache.org/security/CVE-2026-48205.html)
- [GitHub Advisory GHSA-hcm8-x79p-wx2w](https://github.com/advisories/GHSA-hcm8-x79p-wx2w)
- [CVE.org record CVE-2026-48205](https://www.cve.org/CVERecord?id=CVE-2026-48205)
- [NVD entry CVE-2026-48205](https://nvd.nist.gov/vuln/detail/CVE-2026-48205)
- [openwall.com](http://www.openwall.com/lists/oss-security/2026/07/05/19)
- [github.com](https://github.com/apache/camel/commit/bdd40cf23f2b22cd293ddad319069a7b3b3c6c70)
- [issues.apache.org](https://issues.apache.org/jira/browse/CAMEL-23574)

---
Source page: https://erroneo.us/security/cve/CVE-2026-48205/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt