data query logic (Cypher injection) · Improper Neutralization of Special Elements
Source GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 8.1.3 or 8.0.9 soon.
Data as of 20 Nov 2026, 10:33 UTC
Thin evidence
One scorer or none| CNA (Neo4j) | CVSS 4.0 | 8.2 |
|---|
- Patch
- Available – fixed in 8.1.3, 8.0.9
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Spring Data Neo4j and org.springframework.data/spring-data-neo4j to 8.1.3 or 8.0.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Spring Data Neo4jorg.springframework.data:spring-data-neo4j | Affected
| Fixed in
|
| Spring Data Neo4jorg.springframework.data:spring-data-neo4j | Affected
| Fixed in
|
Mavenorg.springframework.data/spring-data-neo4jpkg:maven/org.springframework.data/spring-data-neo4jOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, ensure that applications do not pass unvalidated user input as the orderBy value in custom Cypher queries. Implement strict input validation or sanitization on any user-supplied parameters used in query placeholders to prevent injection. Additionally, consider disabling APOC file export features if not required to reduce risk.
Description
A Cypher injection vulnerability exists in Neo4j Spring Data Neo4j versions 6.1.0 through 8.0.8 and 8.1.0 through 8.1.2. It arises from improper neutralization of special elements in the orderBy placeholder handling for custom queries. This flaw allows a remote attacker to perform blind reads of the database, write read content into new nodes, or write query results to files if APOC and APOC file export features are enabled. Exploitation requires that an application passes unvalidated user input as the orderBy value in a custom Cypher query.