CVE-2026-19869 Privilege Escalation via Dropped Field-Level @authentication
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| neo4j @neo4j/graphql(npm) | >= 5.2.0, < 5.12.15; >= 6.0.0, <= 6.6.4; >= 7.0.0, < 7.6.0 | 5.12.15, 7.6.0 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| neo4j @neo4j/graphql(npm) | >= 7.0.0, < 7.6.0 | 7.6.0 |
| neo4j @neo4j/graphql(npm) | >= 5.2.0, < 5.12.15 | 5.12.15 |
| neo4j @neo4j/graphql(npm) | >= 6.0.0, <= 6.6.4 | No fix listed |
References
- github.com third-party-advisory
- neo4j.com vendor-advisory
- ENISA EUVD EUVD-2026-61047 third-party-advisory