CVE-2026-114405

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (28th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-107231 (ENISA EUVD) · GHSA-f334-8hf4-fmpm (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.7Exploit: None knownExposed services: Not assessed

The vulnerability is patched in versions 36.6 and 37.2 (from the CVE record's solution, Velneo) — apply it.

Improper validation of array index vulnerability in Velneo vServer. This issue affects vServer: from 36.0 before 36.6 and from 37.0 before 37.2.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: The vulnerability is patched in versions 36.6 and 37.2 (from the CVE record's solution, Velneo). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
28th
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.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

The vulnerability is patched in versions 36.6 and 37.2 (from the CVE record's solution, Velneo). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 21, 2026

Last Modified

October 22, 2026

Advisory Details (1)

Auto-updated Oct 21, 2026
Fix named in the CVE record's solution (Velneo).
Web page

Avisos de Seguridad | Velneo

https://velneo.es/avisos-de-seguridad/

Vendor Advisories for CVE-2026-114405(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 / 32× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  4. 2026-11-11 03:37 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  5. 2026-11-10 16:51 UTCEchelonGraph re-scored
  6. 2026-11-10 16:51 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  8. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  9. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  10. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  11. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  12. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  13. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  14. 2026-11-03 20:04 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  15. 2026-11-03 18:02 UTCEchelonGraph re-scored
  16. 2026-11-03 18:02 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  17. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  18. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  19. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  22. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  24. 2026-10-27 20:43 UTCEchelonGraph re-scored
  25. 2026-10-27 20:43 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
Show 15 more
  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-10-25 14:50 UTCEchelonGraph re-scored
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-22 15:48 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  9. 2026-10-21 18:26 UTCEchelonGraph re-scored
  10. 2026-10-21 18:26 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  11. 2026-10-21 17:31 UTCEchelonGraph re-scored
  12. 2026-10-21 17:31 UTCGHSA enrichmentGHSA-f334-8hf4-fmpm · GitHub severity HIGH
  13. 2026-10-21 14:29 UTCEchelonGraph re-scored
  14. 2026-10-21 12:53 UTCMITRE cvelistV5first tracked
  15. 2026-10-21 12:52 UTCEchelonGraph re-scoredFirst assessed: 8.7 HIGH

Frequently asked(5)

What is CVE-2026-114405?
CVE-2026-114405 is a high-severity vulnerability; its CVE record was published on October 21, 2026. Improper validation of array index vulnerability in Velneo vServer. This issue affects vServer: from 36.0 before 36.6 and from 37.0 before 37.2.
When was CVE-2026-114405 made public?
CVE-2026-114405 was made public on October 21, 2026: that is the date its CVE record's CNA, Velneo, gives for when the vulnerability was made public. The CVE record itself was published on October 21, 2026. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-114405 actively exploited?
CVE-2026-114405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114405?
CVE-2026-114405 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-114405?
The CVE record's solution for CVE-2026-114405, written by its CNA Velneo, names the fix: "The vulnerability is patched in versions 36.6 and 37.2". The vendor advisories EchelonGraph has for CVE-2026-114405 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-114405?

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