An improper authentication vulnerability in the is_authenticated function (src/bolt/bolt_api.c) in FalkorDB before 4.20.0 allows a remote unauthenticated attacker to execute graph queries without credentials through the Bolt endpoint. The function decides whether a password is required by issuing an empty AUTH command to Redis and treats only a WRONGPASS error as meaning that a password is required; any other error, such as LOADING while a dataset is being loaded, MASTERDOWN during replication failover, or OOM under memory pressure, causes the client to be treated as authenticated. Only deployments that enable the Bolt endpoint (BOLT_PORT, disabled by default) are affected.
CVE-2026-107910
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-09. A secondary CVSS source baseline 8.1; sources differ by 0.0.
Also known asEUVD-2026-95487 (ENISA EUVD) · GHSA-f2fq-5xqf-g726 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
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."
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHhigh confidence
- EG Risk
- 37EG Risk 37/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity81% × 45%Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.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: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.5%
- EPSS %ILE
- 41st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
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.
The score's inputs: 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 15, 2026
Advisory Details (3)
Auto-updated Oct 9, 2026v4.20.0
Patch available: FalkorDB/FalkorDB v4.20.0
https://github.com/FalkorDB/FalkorDB/releases/tag/v4.20.0commit 0b11a00b34b2 (FalkorDB/FalkorDB)
Fix landed in FalkorDB/FalkorDB commit 0b11a00b34b2 — awaiting tagged release
https://github.com/FalkorDB/FalkorDB/commit/0b11a00b34b25c4d4fdfe55f0a35c8a00593bd7dremove bolt support
Fix merged in FalkorDB/FalkorDB PR #2170 on 2026-07-08 — awaiting tagged release
https://github.com/FalkorDB/FalkorDB/pull/2170Vendor Advisories for CVE-2026-107910(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 9× in last 7d / 51× 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.
- 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-10-27 19:51 UTCEG score recompute
- 2026-10-27 19:51 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 14:54 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-20 19:12 UTCEG score recompute
- 2026-10-20 19:12 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-18 05:07 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-15 17:27 UTCEG score recompute
Show 26 moreShow fewer
- 2026-10-15 17:26 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-15 16:23 UTCEG score recompute
- 2026-10-15 16:22 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-12 04:12 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 16:34 UTCEG score recompute
- 2026-10-11 16:34 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-11 04:55 UTCEG score recompute
- 2026-10-11 04:55 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-10 17:19 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-10 05:42 UTCEG score recompute
- 2026-10-10 05:42 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-09 18:04 UTCEG score recompute
- 2026-10-09 18:04 UTCGHSA enrichmentGHSA-f2fq-5xqf-g726 · GitHub severity CRITICAL · GitHub CVSS 8.1
- 2026-10-09 06:27 UTCEG score recompute
- 2026-10-09 05:24 UTCEG score recomputeFirst assessed: 8.1 HIGH
- 2026-10-09 05:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-107910?
When was the CVE record for CVE-2026-107910 published?
Is CVE-2026-107910 actively exploited?
What is the CVSS score of CVE-2026-107910?
How do I remediate CVE-2026-107910?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-107910
Is Your Infrastructure Affected by CVE-2026-107910?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.