CVE-2026-5423

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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: epss, secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

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

@neo4j/graphql library versions prior to 7.5.6 fail to verify the authenticity of a client-supplied, pre-decoded JWT object passed through GraphQL subscription connectionParams. As a result, any unauthenticated remote client that can open a GraphQL-over-WebSocket connection can forge arbitrary JWT claims (e.g. sub, roles) in connectionParams.jwt and have them accepted as authenticated identity for the purposes of @authentication and @subscriptionsAuthorization directive evaluation. This allows a fully unauthenticated attacker to receive subscription events that should be restricted to specific authenticated roles/users. Upgrade the library to versions 7.5.6+ or 5.12.14+. v6 is end-of-life and will not receive a fix.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github.
generic

CVE-2026-5423

https://neo4j.com/security/CVE-2026-5423
github Patch Available

Subscription Authentication Bypass via Unverified `connectionParams.jwt` in @neo4j/graphql · Advisory · neo4j/graphql · GitHub

https://github.com/neo4j/graphql/security/advisories/GHSA-fcpg-3fw5-vc65

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 52× 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-09-19 07:29 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 04:03 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 00:59 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 06:11 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 04:30 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-14 02:30 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-13 00:56 UTCEG score recompute
  14. 2026-09-11 22:06 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 20:31 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 06:09 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 17:58 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 17:59 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 16:26 UTCEG score recompute
  25. 2026-09-05 03:32 UTCEG score recompute
Show 53 more
  1. 2026-09-04 09:12 UTCEG score recompute
  2. 2026-09-04 05:07 UTCEPSS rescore
  3. 2026-09-03 06:15 UTCEG score recompute
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 18:14 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-31 01:01 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 12:14 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 10:41 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 20:43 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 19:01 UTCEG score recompute
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 15:34 UTCEG score recompute
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 02:36 UTCEG score recompute
  21. 2026-08-24 13:50 UTCEG score recompute
  22. 2026-08-23 12:16 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 10:43 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 09:10 UTCEG score recompute
  27. 2026-08-20 22:55 UTCEPSS rescore
  28. 2026-08-19 18:49 UTCEG score recompute
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-18 15:34 UTCEG score recompute
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 14:19 UTCEG score recompute
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 01:33 UTCEG score recompute
  35. 2026-08-16 14:56 UTCEPSS rescore
  36. 2026-08-16 12:46 UTCEG score recompute
  37. 2026-08-15 11:13 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescore
  39. 2026-08-14 09:40 UTCEG score recompute
  40. 2026-08-13 22:00 UTCEPSS rescore
  41. 2026-08-12 19:20 UTCEG score recompute
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-11 17:46 UTCEG score recompute
  44. 2026-08-11 04:50 UTCEG score recompute
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-09 14:31 UTCEG score recompute
  47. 2026-08-09 13:46 UTCEPSS rescore
  48. 2026-08-09 01:45 UTCEG score recompute
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-08 00:12 UTCEG score recompute
  51. 2026-08-06 16:32 UTCEG score recompute
  52. 2026-08-06 15:31 UTCEG score recompute
  53. 2026-08-06 15:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-5423?
CVE-2026-5423 is a high vulnerability published on August 6, 2026. @neo4j/graphql library versions prior to 7.5.6 fail to verify the authenticity of a client-supplied, pre-decoded JWT object passed through GraphQL subscription connectionParams. As a result, any unauthenticated remote client that can open a GraphQL-over-WebSocket connection can forge arbitrary JWT…
When was CVE-2026-5423 disclosed?
CVE-2026-5423 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5423 actively exploited?
CVE-2026-5423 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 70.5% of all scored CVEs.
What is the CVSS score of CVE-2026-5423?
CVE-2026-5423 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-5423?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5423, 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-5423

Explore →

Is Your Infrastructure Affected by CVE-2026-5423?

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

Start Free Scan →Browse All CVEs