CVE-2026-48203

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
Trending — 3 sources updated this week
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 Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), Improper Input Validation, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel Solr component.

The camel-solr producer copies Exchange message headers whose names begin with the SolrParam. prefix into the parameters of the Solr request, and headers whose names begin with the SolrField. prefix into the fields of the indexed Solr document. The prefix constants (SolrConstants.HEADER_PARAM_PREFIX / HEADER_FIELD_PREFIX) were the plain strings SolrParam. / SolrField.. 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 solr: producer, any HTTP client could therefore set SolrParam.* headers to inject arbitrary Solr request parameters - including shards or stream.url, which cause the Solr server to issue server-side requests to an attacker-chosen URL (server-side request forgery, for example to an internal service or a cloud metadata endpoint), or qt to reach administrative request handlers - and set SolrField.* headers to inject arbitrary fields into indexed documents. 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 set Solr parameters or fields via the raw header prefixes must use CamelSolrParam. / CamelSolrField. instead of SolrParam. / SolrField.. For deployments that cannot upgrade immediately, strip the SolrParam.* and SolrField.* headers from any untrusted ingress before the solr: producer, and set the required Solr parameters and fields 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-48203: Apache Camel: Camel-Solr: The SolrParam. and SolrField. Exchange header prefixes used non-Camel-prefixed names that bypass the HTTP header filter, allowing an HTTP client to inject Solr query parameters (server-side request forgery) and document fields

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

Apache Camel Security Advisory - CVE-2026-48203 - Apache Camel

http://camel.apache.org/security/CVE-2026-48203.html

Vendor Advisories for CVE-2026-48203(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48203?
CVE-2026-48203 is a critical vulnerability published on July 6, 2026. Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'), Improper Input Validation, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel Solr component. The camel-solr producer copies Exchange message headers whose names begin with the…
When was CVE-2026-48203 disclosed?
CVE-2026-48203 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-48203 actively exploited?
CVE-2026-48203 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-48203?
CVE-2026-48203 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-48203?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48203, 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-48203

Explore →

Is Your Infrastructure Affected by CVE-2026-48203?

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

Start Free Scan →Browse All CVEs