CVE-2026-92681
@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
- State
- Published
- Severity
- 9.3 Critical
- Published
- Oct 12, 2026
- Updated
- Oct 16, 2026
- Reserved
- Sep 16, 2026
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 9.3 Critical | 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 | Neo4j |
Weaknesses
- CWE-306 Missing Authentication for Critical Function
Affected Products
| Product | Versions |
|---|---|
@neo4j/graphqlNeo4j |
|
References
- GHSA-8xj4-8gg9-fx9hvendor-advisory
- Fix commit ef69cc6patch
- @neo4j/graphql 7.6.4 release notesrelease-notes
- https://www.npmjs.com/package/@neo4j/graphqlproduct
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.