CVE-2026-107911

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.5EG
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Securin) states them: "Upgrade FalkorDB to version 4.20.0 or later."

A type confusion vulnerability in the _read_flags function (src/commands/cmd_dispatcher.c) in FalkorDB before 4.20.0 allows a remote authenticated attacker who can run GRAPH.QUERY to cause a denial of service and possibly disclose or corrupt memory. The function accepts a --bolt argument from any client and casts the following command argument, a Redis string object, to a Bolt client structure without checking its origin; the result-set code then dereferences pointers read from that object. The argument is parsed even when the Bolt endpoint is disabled, so default configurations are affected.

CVSS v3
7.5
EG Score
7.5HIGHhigh 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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.4% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

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

A fix is available. 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

October 9, 2026

Last Modified

October 9, 2026

Advisory Details (3)

Auto-updated Oct 9, 2026
Patch available. Sources: github_pr, github_commit, github_release.
GitHub release Patch Available

v4.20.0

Patch available: FalkorDB/FalkorDB v4.20.0

https://github.com/FalkorDB/FalkorDB/releases/tag/v4.20.0
GitHub commit

commit 0b11a00b34b2 (FalkorDB/FalkorDB)

Fix landed in FalkorDB/FalkorDB commit 0b11a00b34b2 — awaiting tagged release

https://github.com/FalkorDB/FalkorDB/commit/0b11a00b34b25c4d4fdfe55f0a35c8a00593bd7d
GitHub pull request

remove bolt support

Fix merged in FalkorDB/FalkorDB PR #2170 on 2026-07-08 — awaiting tagged release

https://github.com/FalkorDB/FalkorDB/pull/2170

Vendor Advisories for CVE-2026-107911(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 23× in last 7d / 23× 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-13 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:38 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-12 03:11 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-10-11 20:14 UTCEG score recompute
  6. 2026-10-11 18:26 UTCEG score recompute
  7. 2026-10-11 15:40 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-10-11 15:00 UTCEG score recompute
  9. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-11 04:09 UTCEG score recompute
  11. 2026-10-11 04:09 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-10-10 16:38 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-10-10 05:06 UTCEG score recompute
  15. 2026-10-10 05:06 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-09 17:35 UTCEG score recompute
  18. 2026-10-09 17:35 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-10-09 16:58 UTCEG score recompute
  20. 2026-10-09 16:58 UTCGHSA enrichmentGHSA-g4x7-54hf-p7f3 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-09 06:27 UTCEG score recompute
  22. 2026-10-09 05:24 UTCEG score recomputeFirst assessed: 7.5 HIGH
  23. 2026-10-09 05:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107911?
CVE-2026-107911 is a high-severity vulnerability; its CVE record was published on October 9, 2026. A type confusion vulnerability in the readflags function (src/commands/cmd_dispatcher.c) in FalkorDB before 4.20.0 allows a remote authenticated attacker who can run GRAPH.QUERY to cause a denial of service and possibly disclose or corrupt memory. The function accepts a --bolt argument from any…
When was the CVE record for CVE-2026-107911 published?
The CVE record for CVE-2026-107911 was published on October 9, 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 October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-107911 actively exploited?
CVE-2026-107911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107911?
CVE-2026-107911 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107911?
A fix for CVE-2026-107911 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Securin) states them: "Upgrade FalkorDB to version 4.20.0 or later." The vendor advisories EchelonGraph has for CVE-2026-107911 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-107911?

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

Book a Demo →Browse All CVEs