CVE-2026-92681

@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields

Published Oct 12, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

@neo4j/graphql permits top‑level fields annotated with @cypher to be invoked without respecting @authentication directives that are applied at the schema or type level. When an attacker calls such a field, the Cypher statement runs under the GraphQL service account, giving the attacker the same database access that the service account possesses. This allows both reading and modifying data that would normally be protected by the authentication rules. The weakness is a lack of enforcement of authentication, identified as CWE‑306.

Affected Systems

Affected are installations of Neo4j using the @neo4j/graphql package at versions up to and including 7.6.3. Owners of GraphQL APIs that rely on schema‑level or type‑level @authentication to secure top‑level @cypher fields should confirm they are running at least version 7.6.4, where the enforcement has been corrected.

Risk and Exploitability

The CVSS score of 9.3 indicates a high severity vulnerability with both confidentiality and integrity impacts. The EPSS score is not available, so the likelihood of exploitation is uncertain, but the lack of authentication enforcement makes it trivially exploitable by any caller of the GraphQL endpoint. The vulnerability is not listed in the CISA KEV catalog, but the existence of a public advisory and the critical nature of the flaw mean that it should be treated as a high‑risk exposure. Attackers can target any exposed top‑level @cypher field at the GraphQL service without needing prior authentication, enabling data theft or modification.

Remediation

Vendor Solution

Upgrade @neo4j/graphql to version 7.6.4 or later.


Vendor Workaround

Apply @authentication directly to each top-level @cypher field. Where possible, run the GraphQL service account with least-privilege database permissions.


OpenCVE Recommended Actions

  • Upgrade @neo4j/graphql to 7.6.4 or later.
  • Apply @authentication directives directly to each top‑level @cypher field to enforce access control.
  • Configure the GraphQL service account to use least‑privilege database permissions, limiting the impact of any remaining exposed @cypher fields.

Generated by OpenCVE AI on October 12, 2026 at 16:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Neo4j
Neo4j graphql
Vendors & Products Neo4j
Neo4j graphql
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

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
Neo4j
Published
Updated
Oct 16, 2026, 5:28 PM
Reserved
Sep 16, 2026, 4:17 PM
Status
Awaiting Analysis
Published
Oct 12, 2026, 4:17 PM
Modified
Oct 16, 2026, 7:55 PM