CVE Explore

Auth bypass in Neo4j Graphql

CVE-2026-19869

CVSS
Not scored
Public exploits
None known
EPSS
0.005 · 42.7th percentile
Published
2026-08-18

@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.

Vulnerability class: IDOR (Insecure Direct Object Reference)

Published · last modified .

EPSS exploit prediction

EPSS 0.005, 42.7th percentile (last changed ); unchanged over 30 days. About EPSS.

Affected products

Weakness classification (CWE)

References