Improper Neutralization of Special Elements in Data Query Logic Affecting org.apache.camel:camel-neo4j package, versions [4.10.0,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.33% (25th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JAVA-ORGAPACHECAMEL-17879234
  • published7 Jul 2026
  • disclosed6 Jul 2026
  • creditYu Bao

Introduced: 6 Jul 2026

NewCVE-2026-46591  (opens in a new tab)
CWE-943  (opens in a new tab)

How to fix?

Upgrade org.apache.camel:camel-neo4j to version 4.14.8, 4.18.3, 4.21.0 or higher.

Overview

Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Data Query Logic in the Neo4jProducer.retrieveNodes and deleteNode processes when JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation. An attacker can execute arbitrary Cypher queries and read, modify, or delete any node or relationship in the Neo4j database by supplying specially crafted JSON key names. This is only exploitable if a route maps untrusted input into the CamelNeo4jMatchProperties map, such as by passing a request body as the match map or from a consumer that does not filter inbound Camel* headers, allowing an external sender to influence the header.

Workaround

This vulnerability can be mitigated by validating or allow-listing property names (for example, against the pattern ^[A-Za-z_][A-Za-z0-9_]$) before the Neo4j producer, and ensuring that any consumer feeding such a route filters inbound Camel / camel* headers so the match header cannot be supplied by an external sender.

CVSS Base Scores

version 4.0
version 3.1