Apache Software Foundation Apache Camel Lucene
Apache Camel Lucene: The query control headers used non-Camel-prefixed names (QUERY, RETURN_LUCENE_DOCS) that bypass the HTTP header filter, allowing an HTTP client to inject the full-text search query
Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel Lucene Component. The camel-lucene producer reads the search phrase from an Exchange header (LuceneConstants.HEADER_QUERY) whose value was the plain string QUERY (and RETURN_LUCENE_DOCS for HEADER_RETURN_LUCENE_DOCS). 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 exposes a Lucene query operation behind an HTTP consumer (for example platform-http), any HTTP client could therefore set the QUERY header and have its value executed against the full-text index, overriding the query the route intended to run. Depending on what is indexed, this allows reading documents the request should not have access to (for example a match-all query returns the entire index, or the route's intended per-user filter can be replaced), and expensive regular-expression queries can consume significant CPU. No credentials are required when the HTTP 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 the query via the raw header name must use CamelLuceneQuery (and CamelLuceneReturnLuceneDocs) instead of QUERY / RETURN_LUCENE_DOCS. For deployments that cannot upgrade immediately, strip the attacker-controllable headers before the Lucene producer and set the query from a trusted source (for example removeHeader('QUERY') and removeHeader('RETURN_LUCENE_DOCS'), then setHeader('QUERY', constant(...)) at the start of the route).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.0.0, < 4.14.8
- >= 4.15.0, < 4.18.3
- >= 4.19.0, < 4.21.0
Fixed in 4.14.8, 4.18.3, 4.21.0
Mitigation
Upgrade Apache Camel Lucene to 4.14.8 or 4.18.3 or 4.21.0 or later.
References
- Vendor advisory camel.apache.org/security/CVE-2026-46585.html
Timeline
Days relative to CVE publicationFirst public PoC 9 days after publication; not in CISA KEV. First PoC: oscerd/CVE-2026-46585 (created 15 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| oscerd/CVE-2026-46585 | 15 Jul 2026 +9 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoGET /exploit/attack
- Ports
- 8080
- Seen in
- 1 repo: oscerd/CVE-2026-46585
- Evidence
- oscerd/CVE-2026-46585/README.md:114 oscerd/CVE-2026-46585/README.md:123
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/exploit/attack(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-46585 Apache Software Foundation Apache Camel Lucene exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-46585; classtype:web-application-attack; sid:9804418; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: Apache Software Foundation Apache Camel Lucene exploit attempt (CVE-2026-46585)
id: gg-pocmon-cve-2026-46585-9804418
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-46585. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-46585
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/exploit/attack'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.46585