CVE-2026-92681 @neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
Unauthenticated attackers can execute top-level Cypher queries if schema-level authentication directives are used, bypassing intended access controls.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-92681?
CVE-2026-92681 is a critical missing authorization vulnerability in @neo4j/graphql, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-306
Which versions are affected by CVE-2026-92681?
How do I fix CVE-2026-92681?
No fix has been published for CVE-2026-92681 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-92681 being exploited?
There is no known exploitation of CVE-2026-92681 in the wild and no public exploit code.
Sources
Also known as GHSA-8xj4-8gg9-fx9h.