CVE-2026-48205

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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, 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.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 6, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-48205: Apache Camel: Camel-DNS: The dns.* and term Exchange header constants used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to redirect DNS queries to an attacker-controlled server (server-side request forgery) and enumerate internal

http://www.openwall.com/lists/oss-security/2026/07/05/19
generic

Apache Camel Security Advisory - CVE-2026-48205 - Apache Camel

https://camel.apache.org/security/CVE-2026-48205.html

Vendor Advisories for CVE-2026-48205(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 84× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 16:29 UTCEG score recompute
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 12:49 UTCEG score recompute
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-24 14:18 UTCEPSS rescore
  6. 2026-07-23 14:18 UTCEPSS rescore
  7. 2026-07-23 03:18 UTCEG score recompute
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 15:24 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 02:29 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-17 06:32 UTCGHSA enrichment
  14. 2026-07-17 02:53 UTCGHSA enrichment
  15. 2026-07-16 23:13 UTCGHSA enrichment
  16. 2026-07-16 19:34 UTCGHSA enrichment
  17. 2026-07-16 17:03 UTCEPSS rescore
  18. 2026-07-16 15:37 UTCGHSA enrichment
  19. 2026-07-16 11:50 UTCGHSA enrichment
  20. 2026-07-16 08:11 UTCGHSA enrichment
  21. 2026-07-16 04:31 UTCGHSA enrichment
  22. 2026-07-16 00:51 UTCGHSA enrichment
  23. 2026-07-15 21:10 UTCGHSA enrichment
  24. 2026-07-15 17:31 UTCGHSA enrichment
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 59 more
  1. 2026-07-15 13:41 UTCGHSA enrichment
  2. 2026-07-15 10:01 UTCGHSA enrichment
  3. 2026-07-15 06:22 UTCGHSA enrichment
  4. 2026-07-15 02:43 UTCGHSA enrichment
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-14 22:55 UTCGHSA enrichment
  7. 2026-07-14 19:16 UTCGHSA enrichment
  8. 2026-07-14 15:36 UTCGHSA enrichment
  9. 2026-07-14 11:55 UTCGHSA enrichment
  10. 2026-07-14 08:16 UTCGHSA enrichment
  11. 2026-07-14 04:34 UTCGHSA enrichment
  12. 2026-07-14 00:55 UTCGHSA enrichment
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 21:16 UTCGHSA enrichment
  15. 2026-07-13 17:37 UTCGHSA enrichment
  16. 2026-07-13 13:58 UTCGHSA enrichment
  17. 2026-07-13 10:18 UTCGHSA enrichment
  18. 2026-07-13 06:39 UTCGHSA enrichment
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 02:54 UTCGHSA enrichment
  21. 2026-07-12 23:15 UTCGHSA enrichment
  22. 2026-07-12 19:34 UTCGHSA enrichment
  23. 2026-07-12 15:54 UTCGHSA enrichment
  24. 2026-07-12 12:15 UTCGHSA enrichment
  25. 2026-07-12 08:35 UTCGHSA enrichment
  26. 2026-07-12 05:46 UTCEPSS rescore
  27. 2026-07-12 04:55 UTCGHSA enrichment
  28. 2026-07-12 01:16 UTCGHSA enrichment
  29. 2026-07-11 21:37 UTCGHSA enrichment
  30. 2026-07-11 17:57 UTCGHSA enrichment
  31. 2026-07-11 14:17 UTCGHSA enrichment
  32. 2026-07-11 10:36 UTCGHSA enrichment
  33. 2026-07-11 08:27 UTCEPSS rescore
  34. 2026-07-11 06:55 UTCGHSA enrichment
  35. 2026-07-11 03:16 UTCGHSA enrichment
  36. 2026-07-10 23:37 UTCGHSA enrichment
  37. 2026-07-10 19:58 UTCGHSA enrichment
  38. 2026-07-10 16:19 UTCGHSA enrichment
  39. 2026-07-10 12:39 UTCGHSA enrichment
  40. 2026-07-10 08:57 UTCGHSA enrichment
  41. 2026-07-10 05:18 UTCGHSA enrichment
  42. 2026-07-10 01:34 UTCGHSA enrichment
  43. 2026-07-09 21:53 UTCGHSA enrichment
  44. 2026-07-09 19:10 UTCEPSS rescore
  45. 2026-07-09 18:13 UTCGHSA enrichment
  46. 2026-07-09 14:34 UTCGHSA enrichment
  47. 2026-07-09 10:53 UTCGHSA enrichment
  48. 2026-07-09 07:12 UTCGHSA enrichment
  49. 2026-07-09 03:33 UTCEG score recompute▲ 9.10
  50. 2026-07-09 03:32 UTCGHSA enrichment
  51. 2026-07-08 15:16 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-06 19:44 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 11:43 UTCNVD update
  56. 2026-07-06 10:21 UTCMITRE cvelistV5
  57. 2026-07-06 09:42 UTCNVD update
  58. 2026-07-06 08:52 UTCEG score recompute
  59. 2026-07-06 08:51 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48205?
CVE-2026-48205 is a critical vulnerability published on July 6, 2026. 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…
When was CVE-2026-48205 disclosed?
CVE-2026-48205 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48205 actively exploited?
CVE-2026-48205 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.4% of all scored CVEs.
What is the CVSS score of CVE-2026-48205?
CVE-2026-48205 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-48205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48205, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48205

Explore →

Is Your Infrastructure Affected by CVE-2026-48205?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs