PoC Monitor
← All CVEs
CVE-2026-19869published 18 Aug 2026 16:35 UTCData: JSON · API

Neo4j graphql

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.6high · scored by CNA · CWE-639
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

neo4j graphql
  • >= 7.0.0, < 7.6.0
  • >= 5.2.0, < 5.12.15
  • >= 6.0.0, <= 6.6.4

Fixed in 7.6.0, 5.12.15

Mitigation

Upgrade the library to 7.6.0+ or 5.12.15+. v6 is end-of-life and will not receive a fix. v5 releases prior to 5.2.0 are not affected. For users who cannot upgrade immediately: do not combine a type-level @authentication with a field-level @authentication on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement — instead apply a complete @authentication directive to each root field individually, including the full stricter rule on the sensitive field. Alternatively, enforce the stricter requirement inside the custom resolver's own code.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published18 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.