9.1

CVE-2026-48203: apache software foundation apache camel Improper Input Validation

CVSS: 9.1v3.1CriticalAnalyzed
AliasesGHSA-4h4f-v54q-7pq8
Published 06-07-2026Last modified 06-07-2026

Vulnerability summary

CVE-2026-48203 is a critical (CVSS 9.1) Improper Input Validation vulnerability in apache software foundation apache camel. EPSS estimates a 0.60% chance of exploitation in the next 30 days, higher than 47.6% of scored vulnerabilities.

Overall risk
70/100
0100
High · default modelHow is this calculated?
CVSS score
9.1/10
010
Critical · v3.1 (CVE.org)
EPSS score
0.60%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Timeline

  1. 06-07-2026
    PublishedVulnerability first disclosed.
  2. 06-07-2026
    Last modifiedVulnerability information updated.

Description

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 metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.60%

Chance of exploitation in the next 30 days

Percentile

48%

Versus all other CVEs

30-day change

0.00 pp

From 0.60% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.60%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Apache1 product
  • camel≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0
Apache software foundation1 product
  • apache camel≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0
Org.apache.camel1 product
  • camel-solr≥ 4.0.0, < 4.14.8 | ≥ 4.15.0, < 4.18.3 | ≥ 4.19.0, < 4.21.0

3 vendors · 3 products

References

14 links
Show all 14 references