WaratekVRT Sign in

CVE-2026-46585 Apache Camel

Affected softwareApache Camel
Severity7.5 High CVSS 3.1
Fixed in4.14.8, 4.18.3, 4.21.0
WeaknessImproper input validation (CWE-20)
Published6 Jul 2026
Updated25 Oct 2026

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

Exploitation status

No public exploit

No exploit has been reported in the sources we check. The 1 repository below are public GitHub repositories with fewer than 5 stars.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC 1 indexed, none at 5+ stars
  • EPSS 0.63% chance in 30 days

1 of these are GitHub repositories with fewer than 5 stars. They are listed for reference and don't count toward the exploitation status above.

IndexArtifactStarsFirst seen
GitHub PoC Reproducer for CVE-2026-46585: Apache Camel camel-lucene QUERY header injection enabling authorization bypass / index data exfiltration (fixed in 4.14.8/4.18.3/4.21.0) 2026-07-15

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: apache/camel #23208.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.apache.camel:camel-lucene 4.0.0 4.14.8 unbounded
org.apache.camel:camel-lucene 4.15.0 4.18.3 unbounded
org.apache.camel:camel-lucene 4.19.0 4.21.0 unbounded

Products and versions

2 products, 6 version entries
SourceVendorProductSchemeAffected versions
nvd apache camel generic ≥ 4.0.0 and < 4.14.8 · ≥ 4.15.0 and < 4.18.3 · ≥ 4.19.0 and < 4.21.0
osv org.apache.camel camel-lucene generic ≥ 4.0.0 and < 4.14.8 · ≥ 4.15.0 and < 4.18.3 · ≥ 4.19.0 and < 4.21.0

References

URLTags
https://github.com/apache/camel/pull/23208 WEB
https://github.com/apache/camel/pull/23220 WEB
https://github.com/apache/camel/pull/23232 WEB
https://github.com/apache/camel/commit/16a70d48145605c1a35e909d308bf9e5e2d3e7d8 WEB
https://github.com/apache/camel/commit/349f197115d60e0c180cf9836e08f4aeb5a87872 WEB
https://github.com/apache/camel/commit/878ea07996caff19ed227984bf6cb6cf01983422 WEB
https://camel.apache.org/security/CVE-2026-46585.html WEB
https://github.com/apache/camel PACKAGE
https://github.com/apache/camel/releases/tag/camel-4.14.8 WEB
https://github.com/apache/camel/releases/tag/camel-4.18.3 WEB

Timeline

Published2026-07-06By the CVE Program.
NVD record modified2026-10-25NVD's own last-modified date for this record.