CVE-2026-19869
Received Received - Intake

Authentication Bypass in Neo4j GraphQL Library

Publication date: 2026-08-18

Last updated on: 2026-08-18

Assigner: Neo4j

Description
@neo4j/graphql from 5.2.0 until the patched versions fails to enforce field-level @authentication rules on root custom-resolver fields when a type-level @authentication rule is also present on the same operation type. When both a type-level @authentication (on Query/Mutation) and a field-level @authentication (on a root custom-resolver field within that type) are declared, only the type-level rule is evaluated and the field-level rule is silently discarded. As a result a stricter per-field requirement — such as an admin-role JWT claim (jwt: { roles_INCLUDES: "admin" }) — is never checked, and any client that satisfies the coarser type-level requirement can invoke the more-restricted field. No token forgery is involved: a legitimately issued, correctly signed non-admin token (e.g. roles: ["user"]) is sufficient.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-18
Last Modified
2026-08-18
Generated
2026-09-07
AI Q&A
2026-08-18
EPSS Evaluated
2026-09-06
NVD
CVE-2026-19869
EUVD
EUVD-2026-61047

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
neo4j graphql From 5.2.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the @neo4j/graphql library versions 5.2.0 to 5.12.14, 6.0.0 and above, and 7.0.0 to 7.5.9. It allows field-level authentication rules on custom-resolver fields to be ignored when a type-level authentication rule exists on the same operation type (Query or Mutation). This bypasses intended security checks, enabling users with basic privileges to access restricted fields.

Detection Guidance

Check the version of @neo4j/graphql in your project dependencies. If it falls between 5.2.0 and 5.12.14, 6.0.0 and above, or 7.0.0 to 7.5.9, the system is vulnerable.

Impact Analysis

The vulnerability can lead to unauthorized data access or execution of restricted operations. Attackers with a valid but non-admin token could bypass stricter field-level security rules and access admin-only fields or perform privileged actions, even without forging tokens.

Compliance Impact

This vulnerability may violate compliance requirements that mandate strict access controls and data protection, such as GDPR's principle of least privilege or HIPAA's access control safeguards. Unauthorized data access could result in regulatory penalties or breaches of confidentiality.

Mitigation Strategies

Upgrade to patched versions of @neo4j/graphql (5.12.15 or 7.6.0+). Alternatively, remove type-level @authentication rules if they conflict with field-level rules or enforce stricter requirements in custom resolver code.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19869. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart