CVE-2026-19869

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.6Exploit: None knownExposed services: Not assessed

Upgrade the library to 7.6.0+ or 5.12.15+ (from the CVE record's solution, Neo4j) — apply it.

@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.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
The EG Score, 7.6 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade the library to 7.6.0+ or 5.12.15+ (from the CVE record's solution, Neo4j). Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

Upgrade the library to 7.6.0+ or 5.12.15+ (from the CVE record's solution, Neo4j). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Aug 18, 2026
Fix named in the CVE record's solution (Neo4j). Sources: github.
GitHub advisoryMentions a patch (unverified)

Privilege Escalation via Dropped Field-Level @authentication on Root Custom-Resolver Fields in @neo4j/graphql · Advisory · neo4j/graphql · GitHub

https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 20:06 UTCEG score recompute
  2. 2026-10-11 17:19 UTCEG score recompute
  3. 2026-10-11 14:51 UTCEG score recompute
  4. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-06 21:39 UTCEG score recompute
  10. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-06 08:22 UTCEG score recompute
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-05 11:43 UTCEG score recompute
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-03 17:38 UTCEG score recompute
  16. 2026-10-02 01:28 UTCEG score recompute
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-30 22:50 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-30 09:48 UTCEG score recompute
  21. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-28 23:28 UTCEG score recompute
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-27 21:15 UTCEG score recompute
  25. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 69 more
  1. 2026-09-27 07:56 UTCEG score recompute
  2. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-09-24 16:05 UTCEG score recompute
  4. 2026-09-24 01:52 UTCEG score recompute
  5. 2026-09-22 23:47 UTCEG score recompute
  6. 2026-09-21 21:15 UTCEG score recompute
  7. 2026-09-21 08:12 UTCEG score recompute
  8. 2026-09-20 04:44 UTCEG score recompute
  9. 2026-09-19 02:20 UTCEG score recompute
  10. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-09-18 00:15 UTCEG score recompute
  12. 2026-09-16 21:56 UTCEG score recompute
  13. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-09-15 15:55 UTCEG score recompute
  16. 2026-09-14 00:35 UTCEG score recompute
  17. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-09-12 22:29 UTCEG score recompute
  19. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-09-11 20:23 UTCEG score recompute
  21. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  22. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-09-10 18:17 UTCEG score recompute
  24. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-09 16:11 UTCEG score recompute
  26. 2026-09-09 03:25 UTCEG score recompute
  27. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  28. 2026-09-07 17:11 UTCEG score recompute
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  30. 2026-09-07 04:08 UTCEG score recompute
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  32. 2026-09-05 23:58 UTCEG score recompute
  33. 2026-09-04 21:50 UTCEG score recompute
  34. 2026-09-04 08:16 UTCEG score recompute
  35. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  36. 2026-09-02 16:49 UTCEG score recompute
  37. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  38. 2026-09-02 00:43 UTCEG score recompute
  39. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  40. 2026-09-01 11:41 UTCEG score recompute
  41. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  42. 2026-08-30 20:30 UTCEG score recompute
  43. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  44. 2026-08-30 07:28 UTCEG score recompute
  45. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  46. 2026-08-29 03:50 UTCEG score recompute
  47. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  48. 2026-08-27 20:35 UTCEG score recompute
  49. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  50. 2026-08-26 18:13 UTCEG score recompute
  51. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-08-25 15:44 UTCEG score recompute
  53. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-08-25 02:41 UTCEG score recompute
  55. 2026-08-24 13:39 UTCEG score recompute
  56. 2026-08-23 11:34 UTCEG score recompute
  57. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  58. 2026-08-22 09:28 UTCEG score recompute
  59. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  60. 2026-08-21 07:22 UTCEG score recompute
  61. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  62. 2026-08-20 05:17 UTCEG score recompute
  63. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-08-19 16:14 UTCEG score recompute
  65. 2026-08-18 20:23 UTCEG score recompute
  66. 2026-08-18 19:19 UTCEG score recompute
  67. 2026-08-18 17:21 UTCEG score recompute
  68. 2026-08-18 16:50 UTCEG score recomputeFirst assessed: 7.6 HIGH
  69. 2026-08-18 16:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19869?
CVE-2026-19869 is a high-severity vulnerability; its CVE record was published on August 18, 2026. @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…
When was the CVE record for CVE-2026-19869 published?
The CVE record for CVE-2026-19869 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-19869 actively exploited?
CVE-2026-19869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19869?
CVE-2026-19869 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19869?
The CVE record's solution for CVE-2026-19869, written by its CNA Neo4j, names the fix: "Upgrade the library to 7.6.0+ or 5.12.15+."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19869

Explore →

Is Your Infrastructure Affected by CVE-2026-19869?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs