Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.6

Neo4j GraphQL: Admin Access via Non-Admin Token

CVE-2026-19869 · published 2 months ago
Summary

A security issue affects Neo4j GraphQL from version 5.2.0. An attacker can use a legitimate, non-admin token to access restricted fields, potentially leading to unauthorized access or data modification. To protect your system, update to a patched version of Neo4j GraphQL.

What to do
  • Update neo4j graphql to version 7.6.0 or later.
Affected software
VendorProductAffected versions
neo4j graphql < 7.6.0
Original advisory text
Privilege Escalation via Dropped Field-Level @authentication
@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.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
8.6 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-639Authorization Bypass Through User-Controlled Key
Timeline
Published18 Aug 2026
Updated4 Nov 2026
First seen18 Aug 2026
Sources
CVE-2026-19869 · OSV
GHSA-82m8-p9px-c3x5 · GHSA
CVE-2026-19869 · NVD
CVE-2026-19869 · MITRE
Track software like this
Free during beta