CVE-2026-92681: @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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
@neo4j/graphqlto a version that resolves this vulnerability.Fixed in 7.6.4
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using @neo4j/graphql version 7.6.3 or earlier are exposed if they publish a top-level Query or Mutation field annotated with @cypher and rely on schema-level or type-level @authentication to restrict access.
Does an attacker need credentials or user interaction?
No. The reported vector requires neither privileges nor user interaction; an unauthenticated caller can invoke an affected top-level @cypher field.
What can an unauthenticated caller do through an affected field?
They can execute the Cypher statement configured for that field using the GraphQL service account's privileges. Depending on those privileges and the statement, this may allow data reading or modification.
What can be done before upgrading?
Place @authentication directly on each affected top-level @cypher field, since field-level directives are enforced. Upgrade to version 7.6.4 to obtain the fix.
How can I identify affected fields?
Review the GraphQL schema for top-level Query or Mutation fields with @cypher. Fields that lack a directly applied @authentication directive but are expected to inherit authentication from the schema, Query type, or Mutation type should be treated as affected.