CVE-2026-88410

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-21. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

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

The graph.UDF in FalkorDB (Redis module) v4.20.1 to v4.20.4 is not registered as a write command, leading to unexpected behavior within the application.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Sep 21, 2026
No patch confirmed yet.
generic

UDF hardening: graph.UDF missing write flag, fail-open ASSERT on RDB load, no JS interrupt handler · Issue #2401 · FalkorDB/FalkorDB · GitHub

https://github.com/FalkorDB/FalkorDB/issues/2401

Vendor Advisories for CVE-2026-88410(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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-25 02:35 UTCEG score recompute
  2. 2026-09-25 02:35 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 13:25 UTCEG score recompute
  5. 2026-09-24 13:25 UTCGHSA enrichment
  6. 2026-09-24 13:14 UTCEG score recompute
  7. 2026-09-24 13:14 UTCGHSA enrichment
  8. 2026-09-24 11:40 UTCGHSA enrichment
  9. 2026-09-23 22:31 UTCEG score recompute
  10. 2026-09-23 22:31 UTCGHSA enrichment
  11. 2026-09-23 17:54 UTCEPSS rescore
  12. 2026-09-23 09:21 UTCGHSA enrichment
  13. 2026-09-22 20:12 UTCEG score recompute
  14. 2026-09-22 20:12 UTCGHSA enrichment
  15. 2026-09-22 16:01 UTCEPSS rescore
  16. 2026-09-22 10:27 UTCEG score recompute
  17. 2026-09-22 10:27 UTCGHSA enrichment
  18. 2026-09-21 21:17 UTCEG score recompute
  19. 2026-09-21 21:16 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88410?
CVE-2026-88410 is a high vulnerability published on September 21, 2026. The graph.UDF in FalkorDB (Redis module) v4.20.1 to v4.20.4 is not registered as a write command, leading to unexpected behavior within the application.
When was CVE-2026-88410 disclosed?
CVE-2026-88410 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88410 actively exploited?
CVE-2026-88410 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 73.2% of all scored CVEs.
What is the CVSS score of CVE-2026-88410?
CVE-2026-88410 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-88410?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88410, 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-88410

Explore →

Is Your Infrastructure Affected by CVE-2026-88410?

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

Book a Demo →Browse All CVEs