CVE-2026-48203

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available.
Web page

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
Web page

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

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

Vendor Advisories for CVE-2026-48203(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcamel2026-09-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.camel:camel-solr4.19.0, 4.20.0
  • 4.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 363 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 263 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 17:04 UTCEG score recompute
  2. 2026-10-15 17:04 UTCVendor advisory
  3. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-10-14 11:04 UTCEG score recompute
  6. 2026-10-14 11:04 UTCVendor advisory
  7. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-10-13 09:16 UTCEG score recompute
  9. 2026-10-13 09:16 UTCVendor advisory
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-12 16:01 UTCEG score recompute
  12. 2026-10-12 07:27 UTCVendor advisory
  13. 2026-10-11 19:44 UTCEG score recompute
  14. 2026-10-11 16:58 UTCEG score recompute
  15. 2026-10-11 14:23 UTCEG score recompute
  16. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-09-23 06:26 UTCEG score recompute
  8. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-09-18 06:05 UTCEG score recompute
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-09-13 17:35 UTCEG score recompute
  13. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-09-13 08:45 UTCEG score recompute
  15. 2026-09-12 13:39 UTCEG score recompute
  16. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-06 14:11 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-09-05 23:14 UTCEG score recompute
  23. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  26. 2026-08-30 21:51 UTCEG score recompute
  27. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  28. 2026-08-30 08:27 UTCEG score recompute
  29. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  30. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  31. 2026-08-28 02:44 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  32. 2026-08-27 22:00 UTCEG score recompute
  33. 2026-08-27 22:00 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  35. 2026-08-27 02:21 UTCEG score recompute
  36. 2026-08-27 02:21 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  38. 2026-08-26 13:56 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  39. 2026-08-25 16:12 UTCEG score recompute
  40. 2026-08-25 16:12 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  42. 2026-08-25 12:02 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  43. 2026-08-25 05:07 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  44. 2026-08-25 00:59 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  45. 2026-08-24 20:49 UTCEG score recompute
  46. 2026-08-24 20:49 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  47. 2026-08-24 14:13 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  48. 2026-08-24 10:04 UTCEG score recompute
  49. 2026-08-24 10:04 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  50. 2026-08-24 04:09 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  51. 2026-08-24 00:01 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  52. 2026-08-23 19:52 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  53. 2026-08-23 15:44 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  54. 2026-08-23 11:36 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  55. 2026-08-23 07:28 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  56. 2026-08-23 03:18 UTCEG score recompute
  57. 2026-08-23 03:18 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  58. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  59. 2026-08-22 23:10 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  60. 2026-08-22 19:02 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  61. 2026-08-22 14:45 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  62. 2026-08-22 09:58 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  63. 2026-08-22 05:50 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  64. 2026-08-22 01:20 UTCEG score recompute
  65. 2026-08-22 01:20 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  66. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  67. 2026-08-21 21:12 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  68. 2026-08-21 17:04 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  69. 2026-08-21 12:42 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  70. 2026-08-21 08:27 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  71. 2026-08-21 04:19 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  72. 2026-08-21 00:09 UTCEG score recompute
  73. 2026-08-21 00:09 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1
  74. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  75. 2026-08-20 19:57 UTCGHSA enrichmentGHSA-4h4f-v54q-7pq8 · GitHub severity CRITICAL · GitHub CVSS 9.1

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48203?
CVE-2026-48203 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-48203 published?
The CVE record for CVE-2026-48203 was published on July 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 8, 2026; the record at its source may have been updated since.
Is CVE-2026-48203 actively exploited?
CVE-2026-48203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-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?
A fix for CVE-2026-48203 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48203 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs