@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
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.
CVE-2026-92681
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-92681
@neo4j/graphql
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://github.com/neo4j/graphql",
"vendor": "Neo4j",
"product": "@neo4j/graphql",
"versions": [
{
"status": "affected",
"version": "3.23.0",
"lessThan": "7.6.4",
"versionType": "semver"
}
],
"packageName": "@neo4j/graphql",
"collectionURL": "https://registry.npmjs.org",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-92681
Source reference:
/cveMetadata/cveId
Publisher severity
critical
Source reference: /containers/cna/metrics
- Event
- #32872 · Revision 1
- Added to Heist Feed
- Publisher date