Spring Data Neo4j unauthenticated cypher injection in orderBy placeholder
Affects Spring Data Neo4j 6.1.0 to before 8.0.9 and 8.1.0 to before 8.1.3, in custom Cypher queries that use the orderBy SpEL directive with unvalidated input. Fixed in 8.0.9 and 8.1.3.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.0.9, 8.1.3
- Who is exposed
- Not reported
Summary
Neo4j's Spring Data Neo4j is affected by a Cypher injection flaw in how it handles the orderBy placeholder in custom queries. A remote attacker, without logging in, can send crafted sort order parameters to an application that passes unvalidated user input as the orderBy value, then read database contents through blind reads or write the data into new nodes. If APOC and APOC file export are enabled, the attacker can also write query results to a file in the database's file system.
Written by a model
Original description
Improper neutralization of special elements in data query logic (Cypher injection) in the orderBy placeholder handling for custom queries in Neo4j Spring Data Neo4j versions 6.1.0 through 8.0.8 and 8.1.0 through 8.1.2 allows a remote attacker to read database contents via blind reads, write read content into new nodes, or, if APOC and APOC file export are enabled, to write query results to a file in the database's accessible file system via crafted sort order parameters. Exploitation requires an application that passes unvalidated user input as the orderBy value to a custom Cypher query using the placeholder directive.
What to do
Upgrade to a fixed version: 8.0.9, 8.1.3.
Workaround: Validate any user-supplied orderBy value against an allow list of known property names and sort directions before passing it to Spring Data Neo4j.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125080 (Cypher injection via orderBy placeholder in Spring Data Neo4j custom queries), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125080 (entry last updated 2026-11-20):
Affected:
- Maven package org.springframework.data:spring-data-neo4j: from 6.1.0, fixed in 8.0.9; from 8.1.0, fixed in 8.1.3
Fixed versions: 8.0.9, 8.1.3.
Conditions (all must be true for the bug to be hit):
- Application uses a custom Cypher query containing the orderBy SpEL directive. (source: https://www.cve.org/CVERecord?id=CVE-2026-125080)
- Application passes an unvalidated, attacker-controlled value to the orderBy input of that query. (source: https://www.cve.org/CVERecord?id=CVE-2026-125080)
- Writing query results to a file requires the APOC plugin with APOC file export enabled on the database. (source: https://www.cve.org/CVERecord?id=CVE-2026-125080)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Validate any user-supplied orderBy value against an allow list of known property names and sort directions before passing it to Spring Data Neo4j. (source: https://www.cve.org/CVERecord?id=CVE-2026-125080)
CISA KEV: CVE-2026-125080 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125080 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://neo4j.com/security/CVE-2026-125080
- https://www.cve.org/CVERecord?id=CVE-2026-125080
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125080
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125080"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Maven packages
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | neo4j.com · security/CVE-2026-125080 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-125080 |
| Record | NVD · CVE-2026-125080 |
Questions about CVE-2026-125080
Is CVE-2026-125080 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A value an attacker controls and that is passed to the orderBy input of a custom Cypher query can inject extra Cypher into that query. The injected text is then run as part of the query.
Source: cve.org
Which versions are affected by CVE-2026-125080?
org.springframework.data:spring-data-neo4j (Maven): from 6.1.0 before 8.0.9; from 8.1.0 before 8.1.3.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are Spring Data Neo4j 6.1.0 up to 8.0.9 and 8.1.0 up to 8.1.3. The setup needs a custom Cypher query containing the orderBy SpEL directive, with an unvalidated value passed to it; writing results to a file also needs the APOC plugin with APOC file export enabled. To check, look at the Spring Data Neo4j version in the build file and search the code for custom queries that use the orderBy SpEL directive.
Source: cve.org
How do I fix CVE-2026-125080?
Upgrade Spring Data Neo4j to 8.0.9 or 8.1.3, depending on the release line. Neo4j also recommends 8.2.0 or later. Until then, validate any user-supplied orderBy value against an allow list of known property names and sort directions before passing it to Spring Data Neo4j.
Source: cve.org
Related
- CVE-2026-92681@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
- CVE-2026-92684Aggregation queries can bypass authentication restrictions in @neo4j/graphql
- CVE-2026-92683Incomplete evaluation of multi-condition JWT where filter in @authentication in @neo4j/graphql
- CVE-2026-92682@neo4j/graphql: authorization relationship and connection filters invert the "none" quantifier
- CVE-2026-5423Subscription Authentication Bypass via Unverified connectionParams.jwt
- CVE-2026-19869Privilege Escalation via Dropped Field-Level @authentication
No corrections so far. Something wrong on this page? Report an error.