CVE-2026-19869

HIGHPre-NVD 7.67.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:neo4j, epss
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@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.6(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 18, 2026
Patch available. Sources: github.
github Patch Available

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 / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 18:13 UTCEG score recompute
  3. 2026-08-26 14:46 UTCEPSS rescore
  4. 2026-08-25 15:44 UTCEG score recompute
  5. 2026-08-25 13:48 UTCEPSS rescore
  6. 2026-08-25 02:41 UTCEG score recompute
  7. 2026-08-24 13:39 UTCEG score recompute
  8. 2026-08-23 11:34 UTCEG score recompute
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 09:28 UTCEG score recompute
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 07:22 UTCEG score recompute
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 05:17 UTCEG score recompute
  15. 2026-08-19 17:03 UTCEPSS rescore
  16. 2026-08-19 16:14 UTCEG score recompute
  17. 2026-08-18 20:23 UTCEG score recompute
  18. 2026-08-18 19:19 UTCEG score recompute
  19. 2026-08-18 17:21 UTCEG score recompute
  20. 2026-08-18 16:50 UTCEG score recompute
  21. 2026-08-18 16:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19869?
CVE-2026-19869 is a high vulnerability 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 CVE-2026-19869 disclosed?
CVE-2026-19869 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19869 actively exploited?
CVE-2026-19869 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.1% of all scored CVEs.
What is the CVSS score of CVE-2026-19869?
CVE-2026-19869 has a CVSS v4.0 base score of 7.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-19869?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19869, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs