CVE-2026-48203

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.

• CWE-20
• CWE-74
• CWE-918

• http://camel.apache.org/security/CVE-2026-48203.htmlMitigation, Vendor Advisory
• http://www.openwall.com/lists/oss-security/2026/07/05/17Mailing List, Third Party Advisory

Published

Jul 6, 2026

Last Modified

Jul 8, 2026

Status

Analyzed

• One Click Account Takeover in GranolaHow a notification link broke out of Electron and led to a one-click account takeover.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-48189An improper Input Validation vulnerability in OTRS Customer …5.7
• CVE-2026-4819In Search Guard FLX versions from 1.0.0 up to 4.0.1, the aud…6.5
• CVE-2026-48190An incorrect handling of permissions in OTRS External Interf…3.5
• CVE-2026-48191An incorrect handling of permissions in STORM powered by OTR…3.5
• CVE-2026-48192A vulnerability has been identified in Mendix Studio Pro 10.…6.8
• CVE-2026-4820IBM Maximo Application Suite 9.1, 9.0, 8.11, and 8.10 does n…4.3
• CVE-2026-48204Improper Input Validation, Improper Access Control vulnerabi…9.8
• CVE-2026-48205Improper Input Validation, Server-Side Request Forgery (SSRF…9.1
• CVE-2026-48206Improper Input Validation, Authorization Bypass Through User…5.3
• CVE-2026-48207Deserialization of untrusted data in Apache Fory PyFory. PyF…9.8
• CVE-2026-48208An improper neutralization of active SVG content in OTRS or …6.5
• CVE-2026-48209An improper neutralization of user-controllable input in OTR…7.1