What is CVE-2026-48203?

CVE-2026-48203 is a critical-severity improper input validation vulnerability in org.apache.camel:camel-solr (maven), affecting versions >= 4.0.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2026-48203?

CVE-2026-48203 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.camel:camel-solr are affected by CVE-2026-48203?

org.apache.camel:camel-solr (maven) versions >= 4.0.0, < 4.14.8 is affected.

Is there a fix for CVE-2026-48203?

Yes. CVE-2026-48203 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.

Is CVE-2026-48203 exploitable, and should I be worried?

Whether CVE-2026-48203 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-48203 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-48203 in org.apache.camel:camel-solr

Q: How severe is CVE-2026-48203?

CVE-2026-48203 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.apache.camel:camel-solr are affected by CVE-2026-48203?

org.apache.camel:camel-solr (maven) versions >= 4.0.0, < 4.14.8 is affected.

Q: Is there a fix for CVE-2026-48203?

Yes. CVE-2026-48203 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.

Q: Is CVE-2026-48203 exploitable, and should I be worried?

Whether CVE-2026-48203 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-48203 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-48203?

Upgrade: org.apache.camel:camel-solr to 4.14.8 or later, org.apache.camel:camel-solr to 4.18.3 or later, org.apache.camel:camel-solr to 4.21.0 or later.

Summary

Apache 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

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.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2026-48203 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.8, 4.18.3, 4.21.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.camel:camel-solr (>= 4.0.0, < 4.14.8) org.apache.camel:camel-solr (>= 4.15.0, < 4.18.3) org.apache.camel:camel-solr (>= 4.19.0, < 4.21.0)

Security releases

org.apache.camel:camel-solr → 4.14.8 (maven) org.apache.camel:camel-solr → 4.18.3 (maven) org.apache.camel:camel-solr → 4.21.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.camel:camel-solr to 4.14.8 or later; org.apache.camel:camel-solr to 4.18.3 or later; org.apache.camel:camel-solr to 4.21.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-48203? CVE-2026-48203 is a critical-severity improper input validation vulnerability in org.apache.camel:camel-solr (maven), affecting versions >= 4.0.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2026-48203? CVE-2026-48203 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.camel:camel-solr are affected by CVE-2026-48203? org.apache.camel:camel-solr (maven) versions >= 4.0.0, < 4.14.8 is affected.
Is there a fix for CVE-2026-48203? Yes. CVE-2026-48203 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.
Is CVE-2026-48203 exploitable, and should I be worried? Whether CVE-2026-48203 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-48203 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-48203?
- Upgrade org.apache.camel:camel-solr to 4.14.8 or later
- Upgrade org.apache.camel:camel-solr to 4.18.3 or later
- Upgrade org.apache.camel:camel-solr to 4.21.0 or later