CVE-2026-125080: Cypher injection via orderBy placeholder in Spring Data Neo4j custom queries

Published Nov 20, 2026
·
Updated

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.

Affected Software

1 affected component
VMware Spring Data Neo4j>=6.1.0<=8.0.8, >=8.1.0<=8.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Spring Data Neo4j to a version that resolves this vulnerability.

    Fixed in 8.0.9
  2. Upgrade

    Upgrade Spring Data Neo4j to a version that resolves this vulnerability.

    Fixed in 8.1.3
  3. Upgrade

    Upgrade Spring Data Neo4j to a version that resolves this vulnerability.

    Fixed in 8.2.0

Event History

Nov 20, 2026
CVE Published
via MITRE·08:48 AM
Data Sourced
via MITRE·08:48 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·08:48 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:19 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are exposed to this issue?

Exposure requires an application using a custom Cypher query with the orderBy placeholder directive and passing unvalidated user-controlled input as the orderBy value. Applications that do not use that pattern are not described as affected.

2

What does an attacker need to exploit it?

The attacker needs to be able to supply a crafted sort-order parameter to the vulnerable application. No authentication or user interaction is required according to the supplied severity vector, but exploitation depends on the application forwarding that input without validation.

3

Is file-system impact possible by default?

File writing is only described when both APOC and APOC file export are enabled. Without those conditions, the described impacts are blind reading of database contents and writing read content into new nodes.

4

What can be done if updating is not immediately possible?

Do not pass unvalidated user input into the orderBy value for custom Cypher queries using the placeholder directive. Restrict sort choices to validated, application-defined values; also review whether APOC and APOC file export are enabled.

5

How can teams identify potentially affected code?

Review custom Cypher queries for use of the orderBy placeholder directive, then trace whether the corresponding orderBy value can originate from request parameters or other user-controlled input without validation. The affected version ranges are 6.1.0 through 8.0.8 and 8.1.0 through 8.1.2.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203