CVE-2026-19869: neo4j graphql · Insecure Direct Object Reference
Affects neo4j graphqlSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 7.6.0 or 5.12.15 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.6.0, 5.12.15
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade graphql and @neo4j/graphql to 7.6.0 or 5.12.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| neo4jgraphql | Affected
| Fixed in
|
npm@neo4j/graphqlpkg:npm/@neo4j/graphqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
No explicit patch links or vendor advisory content are provided in the input data. If you cannot patch yet, users should review their use of combined type-level and field-level @authentication rules and avoid relying solely on field-level restrictions when type-level rules are present. Consider applying additional access control checks outside of the library or restricting access at other layers as a temporary mitigation.
Description
CVE-2026-19869 is an authorization bypass vulnerability in the neo4j/graphql library affecting versions 5.2.0 through 5.12.14, 6.0.0 through 6.6.4, and 7.0.0 through 7.5.9. The flaw occurs when both type-level and field-level @authentication rules are defined on the same operation type; only the type-level rule is enforced, causing stricter field-level rules to be ignored. This allows users with a valid token meeting the broader type-level requirements but lacking stricter field-level permissions (e.g., admin role) to access restricted fields. No token forgery is involved, but legitimate non-admin tokens can bypass intended restrictions. The vulnerability has a CVSS 4.0 score of 7.6 (high severity).