CVE-2026-92681: @neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
Neo4j · @neo4j/graphql
Vendor fix available · Affected: Neo4j @neo4j/graphql · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 31% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Neo4j · @neo4j/graphqlfrom 3.23.0 before 7.6.4
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Neo4j
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-92681 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.