CVE-2026-46591 and CVE-2025-66169: Improper Neutralization of Special Elements in Data Query Logic vulnerability in Apache Camel Neo4J component
This Apache advisory covers CVE-2026-46591 and CVE-2025-66169 in Apache Camel Neo4J. Its rating, versions and guidance apply to the bulletin as a whole, not to each of its 2 CVEs.
Key facts
- Bulletin rating
- High, CVSS 8.2
- Affected
- 4.10.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
Description
Improper Neutralization of Special Elements in Data Query Logic vulnerability in Apache Camel Neo4J component. The camel-neo4j producer builds the Cypher WHERE clause for its match/retrieve and delete operations from the CamelNeo4jMatchProperties map.
CVE-2025-66169 addressed Cypher injection through the property values by binding them as query parameters ($paramN), but the property names (the JSON keys of that map) were still concatenated into the query string verbatim in Neo4jProducer.retrieveNodes() and deleteNode().
A property name containing Cypher syntax therefore alters the structure of the executed query.
Where a route maps untrusted input into the CamelNeo4jMatchProperties map - for example by passing a request body as the match map, or from a consumer that does not filter inbound Camel* headers - an attacker who controls the JSON key names can inject arbitrary Cypher and read, modify or delete any node or relationship in the Neo4j database.
The CamelNeo4jMatchProperties header is itself Camel-prefixed and is filtered by the HTTP header-filter strategy, so a plain HTTP client cannot set it directly; the issue is reachable through routes that deliberately or inadvertently carry untrusted data into that header.
This issue affects Apache Camel: from 4.10.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.
Text from the source record.
- 4.10.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
Fix and mitigation
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, do not populate the CamelNeo4jMatchProperties map from untrusted input: validate or allow-list the property names (for example against ^[A-Za-z_][A-Za-z0-9_]*$) before the Neo4j producer, and ensure that any consumer feeding such a route filters inbound Camel* / camel* headers so the match header cannot be supplied by an external sender.
More Apache Software Foundation advisories
CVE-2026-96295Nov 20, 2026Apache Texera: Authenticated users can bypass normal controls on the reading and writingCVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-133325Nov 19, 2026Key exchange without entity authentication vulnerability in Apache TomcatCVE-2026-118436Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118233Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118028Nov 19, 2026Execution After Redirect (EAR) vulnerability in Apache Tomcat in RedirectValve
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.