CVE-2026-19869
Privilege Escalation via Dropped Field-Level @authentication
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.
INFO
Published Date :
Aug. 18, 2026, 5:16 p.m.
Last Modified :
Aug. 18, 2026, 8:17 p.m.
Remotely Exploit :
Yes !
Source :
3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 4.0 | HIGH | 3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6 | ||||
| CVSS 4.0 | HIGH | 3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6 |
Solution
- Update @neo4j/graphql to a patched version.
- Verify field-level authentication rules are enforced.
- Review type and field level authentication configurations.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-19869.
| URL | Resource |
|---|---|
| https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5 | |
| https://neo4j.com/security/CVE-2026-19869 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-19869 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-19869
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-19869 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-19869 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 18, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2026-19869', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3', 'timestamp': '2026-08-18T19:09:25.351012Z'} -
New CVE Received by 3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6
Aug. 18, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://github.com/neo4j/graphql', 'vendor': 'neo4j', 'product': 'graphql', 'versions': [{'status': 'affected', 'version': '7.0.0', 'lessThan': '7.6.0', 'versionType': 'semver'}, {'status': 'affected', 'version': '5.2.0', 'lessThan': '5.12.15', 'versionType': 'semver'}, {'status': 'affected', 'version': '6.0.0', 'versionType': 'semver', 'lessThanOrEqual': '6.6.4'}], 'packageName': '@neo4j/graphql', 'collectionURL': 'https://registry.npmjs.org', 'defaultStatus': 'unaffected'}] Added 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. Added CVSS V4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CWE CWE-639 Added Reference https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5 Added Reference https://neo4j.com/security/CVE-2026-19869