Skip to main content
Menu
CVEs

Neo4j Enterprise Edition remote code execution in index queries

CVE-2026-102770EUVD-2026-130328Published November 19, 2026, updated

5.1MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2026.10.0
Who is exposed
Not reported

Summary

Neo4j Enterprise Edition's fulltext and vector index query generator in its sharded property database fails to neutralize special characters. An authenticated user with access, index-creation, and name-management privileges can inject Cypher through a crafted index name containing a single quote. Over the network, the injected Cypher runs in the session of any user who later queries that index, and it can only do what that querying user is permitted to do, after that user takes action.

Written by a model

Original description

Improper neutralization of special elements in data query logic (Cypher injection) in the fulltext and vector index query generator of the sharded property database in Neo4j Enterprise Edition 2026.07.0 before 2026.10.0 allows an authenticated user holding ACCESS, CREATE INDEX and NAME MANAGEMENT privileges to inject Cypher that is accepted for execution on a property shard, in the session of any user who later queries the index, via a crafted index name containing a single quote. The impact is bounded by the privileges of the querying user.

What to do

Upgrade to a fixed version: 2026.10.0.

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-102770 (Neo4j Enterprise Edition: stored Cypher injection via index name in sharded property database), 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-102770 (entry last updated 2026-11-19):
Affected:
- Neo4j Neo4j Enterprise Edition: from 2026.07.0, fixed in 2026.10.0
Fixed versions: 2026.10.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-102770 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102770 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://neo4j.com/security/CVE-2026-102770
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-102770
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-102770"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisoryneo4j.com · security/CVE-2026-102770
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-102770
RecordNVD · CVE-2026-102770

Questions about CVE-2026-102770

Is CVE-2026-102770 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

Which versions are affected by CVE-2026-102770?

Neo4j Enterprise Edition: from 2026.07.0 before 2026.10.0.

Source: cve.now feed data

How do I fix CVE-2026-102770?

Upgrade to a fixed version: 2026.10.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.