CVE-2026-48203: CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in Apache Software Foundation Apache Camel
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.
AI Analysis
Technical Summary
Apache Camel Solr component improperly handles HTTP headers starting with SolrParam. and SolrField. prefixes, allowing these headers to pass unchecked into Solr requests. This enables an attacker to inject arbitrary Solr request parameters, including those that trigger server-side request forgery (SSRF) or access administrative endpoints, and to inject arbitrary fields into indexed documents. The vulnerability exists because the header filtering strategy does not block these prefixes, allowing unauthenticated HTTP clients to exploit this when bridging HTTP consumers to solr: producers. Affected versions include 4.0.0 through before 4.14.8, 4.15.0 through before 4.18.3, and 4.19.0 through before 4.21.0. The issue is fixed in Apache Camel 4.14.8, 4.18.3, and 4.21.0. Mitigation includes upgrading to these versions or filtering out SolrParam.* and SolrField.* headers from untrusted sources and using CamelSolrParam. / CamelSolrField. prefixes instead.
Potential Impact
An attacker can exploit this vulnerability to perform injection attacks by setting arbitrary Solr request parameters and fields via HTTP headers. This includes the ability to cause the Solr server to make server-side requests to attacker-controlled URLs (SSRF), potentially accessing internal services or cloud metadata endpoints. Additionally, attackers can reach administrative request handlers and inject arbitrary fields into indexed documents. No authentication is required if the HTTP consumer is unauthenticated, increasing the risk of exploitation in exposed environments.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.21.0. Users are strongly recommended to upgrade to one of these fixed versions. After upgrading, routes must use the CamelSolrParam. and CamelSolrField. prefixes instead of SolrParam. and SolrField. for setting Solr parameters and fields. For environments where immediate upgrade is not possible, it is advised to strip SolrParam.* and SolrField.* headers from any untrusted ingress traffic before the solr: producer and set required parameters and fields from trusted sources within the route. This mitigates the risk of injection and SSRF attacks.
CVE-2026-48203: CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in Apache Software Foundation Apache Camel
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 v3.1
Score 9.1critical
Affected software
pkg:maven/Apache Software Foundation/org.apache.camel:camel-solrRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache Camel Solr component improperly handles HTTP headers starting with SolrParam. and SolrField. prefixes, allowing these headers to pass unchecked into Solr requests. This enables an attacker to inject arbitrary Solr request parameters, including those that trigger server-side request forgery (SSRF) or access administrative endpoints, and to inject arbitrary fields into indexed documents. The vulnerability exists because the header filtering strategy does not block these prefixes, allowing unauthenticated HTTP clients to exploit this when bridging HTTP consumers to solr: producers. Affected versions include 4.0.0 through before 4.14.8, 4.15.0 through before 4.18.3, and 4.19.0 through before 4.21.0. The issue is fixed in Apache Camel 4.14.8, 4.18.3, and 4.21.0. Mitigation includes upgrading to these versions or filtering out SolrParam.* and SolrField.* headers from untrusted sources and using CamelSolrParam. / CamelSolrField. prefixes instead.
Potential Impact
An attacker can exploit this vulnerability to perform injection attacks by setting arbitrary Solr request parameters and fields via HTTP headers. This includes the ability to cause the Solr server to make server-side requests to attacker-controlled URLs (SSRF), potentially accessing internal services or cloud metadata endpoints. Additionally, attackers can reach administrative request handlers and inject arbitrary fields into indexed documents. No authentication is required if the HTTP consumer is unauthenticated, increasing the risk of exploitation in exposed environments.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.21.0. Users are strongly recommended to upgrade to one of these fixed versions. After upgrading, routes must use the CamelSolrParam. and CamelSolrField. prefixes instead of SolrParam. and SolrField. for setting Solr parameters and fields. For environments where immediate upgrade is not possible, it is advised to strip SolrParam.* and SolrField.* headers from any untrusted ingress traffic before the solr: producer and set required parameters and fields from trusted sources within the route. This mitigates the risk of injection and SSRF attacks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-21T08:58:37.029Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b6cae27e9c79719252373
Added to database: 07/06/2026, 08:51:58 UTC
Last enriched: 07/06/2026, 09:08:14 UTC
Last updated: 07/06/2026, 23:08:04 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.