Skip to content
VulniPulse
High7.5Apache Software Foundation

CVE-2026-46585: Apache Camel Lucene authorization bypass

This Apache advisory covers CVE-2026-46585 in Apache Camel Lucene.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N · base score 7.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-20 Improper Input Validation
  • CWE-639 Authorization Bypass Through User-Controlled Key
EPSS
0.63% chance of exploitation in the next 30 days (51st percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
4.0.0 through 4.14.8; 4.15.0 through 4.18.3; 4.19.0 through 4.21.0.
Fixed in
4.21.0, 4.14.8, 4.18.3
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationMessaging

Description

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.

Text from the source record.

Affected versions
  • 4.0.0 through 4.14.8
  • 4.15.0 through 4.18.3
  • 4.19.0 through 4.21.0.

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-46585

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are recommended to upgrade to version 4.21.0, which fixes the issue.
  • 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).

Apache Software Foundation advisories, July 2026All Apache Software Foundation advisories

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)