CVE-2026-46585

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).

• CWE-20
• CWE-639

• https://camel.apache.org/security/CVE-2026-46585.htmlVendor Advisory
• http://www.openwall.com/lists/oss-security/2026/07/05/12Mailing List, Third Party Advisory

Published

Jul 6, 2026

Last Modified

Jul 8, 2026

Status

Analyzed

• Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-46579A flaw was found in the OpenShift Router. When a Route has `…7.5
• CVE-2026-4658The Essential Blocks – Page Builder Gutenberg Blocks, Patter…6.4
• CVE-2026-46580In Eclipse Theia versions prior to 1.71.0, files matching th…8.8
• CVE-2026-46581In Eclipse Mojarra versions 2.3 and following, URL handing i…7.5
• CVE-2026-46582In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a re…3.7
• CVE-2026-46584Improper Input Validation, Exposure of Sensitive Information…3.7
• CVE-2026-46586Improper Control of Generation of Code ('Code Injection'), I…8.8
• CVE-2026-46587Improper Input Validation vulnerability in Apache Camel. Th…7.3
• CVE-2026-46588Improper Input Validation vulnerability in Apache Camel. Th…7.3
• CVE-2026-4659The Unlimited Elements for Elementor plugin for WordPress is…7.5
• CVE-2026-46590Deserialization of Untrusted Data vulnerability in Apache Ca…8.8
• CVE-2026-46591Improper Neutralization of Special Elements in Data Query Lo…8.2