Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade @neo4j/graphql to version 7.6.4 or later.
Workaround
Apply @authentication directly to each top-level @cypher field. Where possible, run the GraphQL service account with least-privilege database permissions.
Mon, 12 Oct 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | @neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Neo4j
Published:
Updated: 2026-10-12T15:09:49.653Z
Reserved: 2026-09-16T16:17:17.929Z
Link: CVE-2026-92681
No data.
Status : Received
Published: 2026-10-12T16:17:07.323
Modified: 2026-10-12T16:17:07.323
Link: CVE-2026-92681
No data.
OpenCVE Enrichment
Updated: 2026-10-12T16:45:14Z