CVE-2026-46591: Apache Camel: Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation, allowing Cypher injection (incomplete remediation of CVE-2025-66169)
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.
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. 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camel Neo4J componentto a version that resolves this vulnerability.Fixed in 4.21.0 - Upgrade
Upgrade
Apache Camel Neo4J componentto a version that resolves this vulnerability.Fixed in 4.14.8 - Upgrade
Upgrade
Apache Camel Neo4J componentto a version that resolves this vulnerability.Fixed in 4.18.3 - Configuration
For routes/deployments that cannot upgrade immediately, validate or allow-list the JSON keys (property names) used in the CamelNeo4jMatchProperties map against ^[A-Za-z_][A-Za-z0-9_]*$ before they reach the Neo4j producer so they are not concatenated verbatim into the Cypher WHERE clause.
camel-neo4j producer (Neo4jProducer.retrieveNodes()/deleteNode()) CamelNeo4jMatchProperties map property-name validation/allow-list = Allow-list property names to match ^[A-Za-z_][A-Za-z0-9_]*$ before building the Cypher WHERE clause - Compensating control
Ensure any consumer that feeds Camel routes filters inbound Camel* / camel* headers so the CamelNeo4jMatchProperties header cannot be supplied by an external sender.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46591?
CVE-2026-46591 has a risk severity rating of 61.
How do I fix CVE-2026-46591?
To fix CVE-2026-46591, ensure that the Camel-Neo4j component is updated to a version that addresses the Cypher injection vulnerability.
What components are affected by CVE-2026-46591?
CVE-2026-46591 affects the Apache Camel Neo4j component, specifically the camel-neo4j producer.
What type of vulnerability is CVE-2026-46591?
CVE-2026-46591 is categorized as an Improper Neutralization of Special Elements in Data Query Logic vulnerability.
Is CVE-2026-46591 related to any previous vulnerabilities?
Yes, CVE-2026-46591 is an incomplete remediation of Cypher injection vulnerabilities previously addressed in CVE-2025-66169.