CVE-2026-46591: Apache Camel Neo4j Cypher Injection Vulnerability – HIGH Severity Patch

Technical summary

CVE-2026-46591 is an improper neutralization of special elements in query logic (CWE-943) affecting the Neo4j producer in Apache Camel. The vulnerability exists in the Neo4jProducer.retrieveNodes() and deleteNode() methods, which build Cypher WHERE clauses by concatenating property names from the CamelNeo4jMatchProperties map directly into the query string. CVE-2025-66169 previously addressed injection through property values by parameterizing them ($paramN notation), but property names (JSON object keys) bypass this protection and are concatenated verbatim. An attacker controlling these keys can break the query syntax boundary and inject arbitrary Cypher clauses. The CamelNeo4jMatchProperties header is Camel-prefixed, so standard HTTP clients cannot set it directly; however, routes that deserialize untrusted input (request bodies, non-filtered consumer headers) into that map create an exploitable path. Vulnerable versions: 4.10.0–4.14.7, 4.15.0–4.18.2, 4.19.0–4.20.x.

Business impact

Organizations using Apache Camel to integrate with Neo4j databases face a high-severity breach risk if they accept untrusted input in Neo4j match operations. A successful attack grants an unauthenticated remote adversary read and write access to the entire Neo4j graph, potentially exposing sensitive relationships, properties, and entities stored in the database. Attackers could extract intellectual property, customer data, or system topology information, or corrupt database integrity by modifying or deleting nodes and relationships. This is particularly critical for applications using Neo4j to store authorization graphs, identity data, or business-critical relationship metadata. The attack requires no authentication and can be exploited in-band during normal request processing, making it immediately actionable in production environments that have not patched.

Affected systems

Apache Camel versions 4.10.0 through 4.20.x are affected, specifically: versions 4.10.0 to 4.14.7 (4.14.x stream), 4.15.0 to 4.18.2 (4.18.x stream), and 4.19.0 to 4.20.x. The vulnerability only manifests in deployments that use the camel-neo4j component and route untrusted input into the CamelNeo4jMatchProperties map. This typically occurs in routes that deserialize JSON request bodies directly as the match map, or that accept inbound Camel* headers from consumers without filtering. Deployments using Camel for other purposes or with hardcoded Neo4j match criteria are not affected.

Exploitability

Exploitability is high. The attack surface is straightforward: an attacker who can control JSON property names or unfiltered Camel headers in a route feeding the Neo4j producer can inject Cypher syntax. Network access is required, but no authentication or special privileges are needed. The injected Cypher can be crafted to perform any operation the Neo4j database user account permits. Proof-of-concept payloads are trivial to construct (e.g., property names like '} OR 1=1 OR {'). The attack is not yet in the CISA KEV catalog, but the simplicity and impact make it a probable target if public exploitation code emerges. Detection may be challenging because malicious input arrives as normal JSON, and logs may not immediately reveal the Cypher injection unless queries are instrumented at the database level.

Remediation

Upgrade to Apache Camel 4.14.8 (if on 4.14.x LTS), 4.18.3 (if on 4.18.x), or 4.21.0+ (for latest features). For deployments unable to patch immediately, implement strict input validation on property names before the Neo4j producer: validate against a whitelist pattern such as ^[A-Za-z_][A-Za-z0-9_]*$ to ensure only valid Cypher identifiers are used. Additionally, ensure any Camel consumer feeding the Neo4j route strips or filters inbound Camel*/camel* headers so that external senders cannot inject the CamelNeo4jMatchProperties header. Consider using immutable or read-only Camel configuration objects to reduce the risk of inadvertent mutation from untrusted input.

Patch guidance

Patches are available in Camel 4.14.8, 4.18.3, and 4.21.0. The fix involves parameterizing or escaping property names in the Cypher query construction, similar to the earlier fix for property values. Verify patched versions against the official Apache Camel release notes and advisory. If you are on a supported LTS stream (4.14.x or 4.18.x), apply the corresponding patch release. For new deployments, use 4.21.0 or later. After patching, restart affected Camel applications and verify that Neo4j integration tests pass, as the fix may affect query structure in edge cases. No database migration or data remediation is required by the patch itself, but consider auditing recent Neo4j audit logs for suspicious query patterns if the deployment was publicly accessible before patching.

Detection guidance

Monitor Camel route logs for warnings or errors during Neo4j producer execution, particularly any messages indicating Cypher syntax errors or unexpected query structures. Enable Neo4j database query logging and audit trails; look for Cypher queries with unexpected WHERE clause structures, injected UNION/OR predicates, or attempts to access unauthorized nodes. Network-level detection is difficult because the exploit payload is embedded in normal JSON. Implement input validation at the application level: before routing data to the Neo4j producer, log and reject any JSON objects with property names that do not match expected patterns or that contain Cypher keywords (e.g., 'WHERE', 'MATCH', 'DELETE', 'OR', '}'). Search your codebase for routes that directly pass request.body or unauthenticated headers into CamelNeo4jMatchProperties to identify vulnerable patterns. Correlate spike in Neo4j query errors with inbound request volume to detect blind injection attempts.

Why prioritize this

This is a high-priority patch for any organization using Camel with Neo4j. The CVSS score of 8.2 reflects high integrity and confidentiality risk with no complexity barriers to exploitation. The vulnerability is network-reachable, requires no credentials, and provides direct database access. Although it is not yet in the KEV catalog, the combination of ease of exploitation, high impact (full database compromise), and likely public tooling when disclosed makes this a critical remediation target. Organizations should treat this as urgent if their Camel deployments accept untrusted input for Neo4j operations. Even organizations on older versions of Camel should backport or upgrade to address this before it becomes a common attack vector.

Risk score, explained

CVSS 3.1 score of 8.2 (HIGH) is driven by: (1) Network-based attack vector (AV:N) requiring only network access, no local access; (2) Low attack complexity (AC:L) because the exploit requires only crafted JSON property names, no advanced techniques; (3) No privileges required (PR:N) because untrusted external input can trigger the vulnerability; (4) No user interaction (UI:N) needed; (5) High integrity impact (I:H) because attackers can modify or delete any Neo4j node or relationship; (6) Low confidentiality impact (C:L) because direct data exfiltration is possible but the primary threat is manipulation. The scope is unchanged (S:U). The score does not account for KEV or active exploitation at publication, but the severity is justified by the directness and scope of database compromise.

Frequently asked questions