PT-2026-55899 · Apache · Apache Camel
CVSS v2.0
9.4
Critical
| Vector | AV:N/AC:L/Au:N/C:C/I:C/A:N |
Name of the Vulnerable Software and Affected Versions
Apache Camel versions 4.0.0 through 4.14.7
Apache Camel versions 4.15.0 through 4.18.2
Apache Camel versions 4.19.0 through 4.20.9
Description
An injection and Server-Side Request Forgery (SSRF) issue exists in the Apache Camel Solr component. The
camel-solr producer copies Exchange message headers starting with the SolrParam. prefix into Solr request parameters and those starting with SolrField. into indexed Solr document fields. Because these prefixes do not start with the Camel or camel namespace, the HttpHeaderFilterStrategy allows them to pass from inbound HTTP requests into the Exchange. In routes bridging an HTTP consumer to a solr: producer, an unauthenticated attacker can inject arbitrary Solr request parameters via SolrParam.* headers—such as shards or stream.url to trigger SSRF toward internal services or cloud metadata endpoints, or qt to access administrative handlers—and inject arbitrary fields into documents via SolrField.* headers.Recommendations
Upgrade Apache Camel versions 4.0.0 through 4.14.7 to version 4.14.8.
Upgrade Apache Camel versions 4.15.0 through 4.18.2 to version 4.18.3.
Upgrade Apache Camel versions 4.19.0 through 4.20.9 to version 4.21.0.
After upgrading, update routes that set Solr parameters or fields to use
CamelSolrParam. and CamelSolrField. instead of SolrParam. and SolrField..
As a temporary mitigation, strip SolrParam.* and SolrField.* headers from untrusted ingress before they reach the solr: producer and set required parameters from a trusted source within the route.Exploit
Fix
RCE
Special Elements Injection
SSRF
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Apache Camel