Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-48203 – SSRF and Header Injection – Apache Camel camel-solr 4.0.0–4.20.x

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-48203 is a critical Server-Side Request Forgery (SSRF) and header injection vulnerability in the Apache Camel camel-solr component, rated CVSS 9.1 (Critical). The flaw allows any unauthenticated HTTP client to inject arbitrary Solr request parameters and document fields by sending crafted HTTP headers, enabling SSRF attacks against internal services and cloud metadata endpoints. Exploitation requires no privileges or user interaction and is fully remote.

Technical details

  • Root cause: The camel-solr producer maps Exchange message headers prefixed with SolrParam. directly into Solr request parameters, and headers prefixed with SolrField. directly into the fields of indexed Solr documents. Because neither prefix begins with Camel or camel, Apache Camel’s HttpHeaderFilterStrategy — which only blocks headers in the Camel namespace — does not strip them at the HTTP boundary. Untrusted inbound HTTP headers therefore flow straight into the downstream Solr producer.
  • Trigger condition: A Camel route must bridge an HTTP consumer (e.g., platform-http, camel-jetty, camel-undertow, or camel-servlet) into a solr: producer with no authentication on the ingress consumer.
  • Attack vector: An unauthenticated remote attacker sends an HTTP request carrying SolrParam.* headers (e.g., SolrParam.shards, SolrParam.stream.url, SolrParam.qt) or SolrField.* headers to the exposed Camel HTTP endpoint.
  • Impact:
    • SSRF: Setting SolrParam.shards or SolrParam.stream.url causes the backend Solr server to issue HTTP requests to an attacker-controlled URL, enabling access to internal services or cloud instance metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254).
    • Administrative handler access: Setting SolrParam.qt redirects the Solr request to privileged administrative request handlers that are normally restricted.
    • Document field injection: Setting SolrField.* headers allows an attacker to inject arbitrary fields into documents indexed by Solr, corrupting search data or poisoning the index.

Affected software

  • Apache Camel 4.0.0 through 4.14.7
  • Apache Camel 4.15.0 through 4.18.2
  • Apache Camel 4.19.0 through 4.20.x

Severity

CVSS v3.1 Base Score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate — apply the vendor patch:
    • Upgrade to Apache Camel 4.21.0 (recommended for all users).
    • If on the 4.14.x LTS stream, upgrade to 4.14.8.
    • If on the 4.18.x stream, upgrade to 4.18.3.
    • After upgrading, routes that set Solr parameters or fields via header prefixes must be updated to use CamelSolrParam. and CamelSolrField. in place of the old SolrParam. and SolrField. prefixes.
  • If immediate patching is not possible — apply the following workarounds:
    • Strip all SolrParam.* and SolrField.* headers from any untrusted ingress traffic before the solr: producer processes the Exchange.
    • Set required Solr parameters and fields from a trusted, internal source within the route rather than from inbound HTTP headers.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge