CVE-2026-92681
@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
- Critical 9.3
Description
In @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema level or on the Query or Mutation types are silently ignored for top-level fields annotated with @cypher. Only @authentication directives placed directly on the individual fields are enforced. An application that exposes a top-level @cypher field and relies on schema-level or type-level @authentication to protect it allows unauthenticated callers to invoke the field and run the configured Cypher statement with the privileges of the GraphQL service account, which may permit reading and modifying data. Fixed in 7.6.4.
Key facts
- Published
- 12 Oct 2026
- Last changed
- 16 Oct 2026
- Assigned by
- Neo4j
- EPSS
- 0.37% likely to be exploited in the next 30 days, higher than 31.499% of CVEs (scores for 18 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: yes; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 9.3CVSS 4.0, Criticalfrom the CNA (Neo4j)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Neo4j | @neo4j/graphql |
|
Timeline
- 12 Oct 2026 Published