CVE-2026-19869 Privilege Escalation via Dropped Field-Level @authentication
Attackers with valid non-admin tokens can access restricted fields because field-level authentication rules are ignored when type-level rules exist.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-19869?
CVE-2026-19869 is a high-severity missing authorization vulnerability in neo4j graphql, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-639
Which versions are affected by CVE-2026-19869?
How do I fix CVE-2026-19869?
No fix has been published for CVE-2026-19869 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-19869 being exploited?
There is no known exploitation of CVE-2026-19869 in the wild and no public exploit code.
Sources
Also known as GHSA-82m8-p9px-c3x5.