CVE-2026-118650

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-28. 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
Elevated

Also known asEUVD-2026-112404 (ENISA EUVD) · GHSA-375p-5qhx-8wq4 (GitHub Security Advisories) · GO-2026-6873 (OSV.dev)Source: ENISA EUVD

7.5EG
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).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Echo is a Go web framework. Prior to 4.16.0 and 5.4.0, a globally mounted middleware.Static instance can interpret an encoded request path differently from Echo's router because the router matches the still-encoded path while the static handler uses the decoded URL.Path. The advisory demonstrates an encoded slash resolving to a file under the static root through the global static middleware, but the source is internally inconsistent about whether a route or group guard protects the corresponding literal path in that global-mount configuration. This issue is fixed in 4.16.0 and 5.4.0.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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 28, 2026

Last Modified

November 2, 2026

Advisory Details (5)

Auto-updated Oct 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

middleware.Static: `%2F`-encoded path bypasses route/group middleware guarding a statically-served path (incomplete fix of CVE-2026-55677); `EnablePathUnescaping` docstring over-promises · Advisory · labstack/echo · GitHub

https://github.com/labstack/echo/security/advisories/GHSA-375p-5qhx-8wq4
GitHub release Patch Available

v5.4.0

Patch available: labstack/echo v5.4.0

https://github.com/labstack/echo/releases/tag/v5.4.0
GitHub release Patch Available

v4.16.0

Patch available: labstack/echo v4.16.0

https://github.com/labstack/echo/releases/tag/v4.16.0
GitHub commit Patch Available

commit fc410094b2f3 (labstack/echo)

Patch available: labstack/echo v5.4.0 (contains commit fc410094b2f3)

https://github.com/labstack/echo/commit/fc410094b2f3415cf2bf5204082137b205bfd5af
GitHub commit Patch Available

commit b838391e2ead (labstack/echo)

Patch available: labstack/echo v4.16.0 (contains commit b838391e2ead)

https://github.com/labstack/echo/commit/b838391e2eade87ae7e5a09d7bb5087bec271ec1

Vendor Advisories for CVE-2026-118650(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/labstack/echo/v4 @ 4.16.0 (fixes < 4.16.0)—ghsa
gogithub.com/labstack/echo/v5 @ 5.4.0 (fixes < 5.4.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/labstack/echo/v4—
  • every version up to 4.16.0: fixed in 4.16.0
—
github.com/labstack/echo/v5—
  • every version up to 5.4.0: fixed in 5.4.0
  • 5.0.0 up to 5.4.0: fixed in 5.4.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 22× 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 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). "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.4% · 34th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-11-10 07:56 UTCEchelonGraph re-scored
  6. 2026-11-10 07:56 UTCGHSA enrichmentGHSA-375p-5qhx-8wq4 · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-11-02 21:25 UTCEchelonGraph re-scored
  15. 2026-11-02 21:25 UTCGHSA enrichmentGHSA-375p-5qhx-8wq4 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-02 20:48 UTCEchelonGraph re-scored
  17. 2026-11-02 20:48 UTCGHSA enrichmentGHSA-375p-5qhx-8wq4 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  20. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-375p-5qhx-8wq4 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-01 07:59 UTCEchelonGraph re-scored
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-28 20:27 UTCEchelonGraph re-scored
Show 3 more
  1. 2026-10-28 20:01 UTCENISA EUVD ID recordedEUVD-2026-112404 · Source: ENISA EUVD
  2. 2026-10-28 19:28 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  3. 2026-10-28 19:28 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-118650?
CVE-2026-118650 is a high-severity vulnerability; its CVE record was published on October 28, 2026. Echo is a Go web framework. Prior to 4.16.0 and 5.4.0, a globally mounted middleware.Static instance can interpret an encoded request path differently from Echo's router because the router matches the still-encoded path while the static handler uses the decoded URL.Path. The advisory demonstrates…
When was the CVE record for CVE-2026-118650 published?
The CVE record for CVE-2026-118650 was published on October 28, 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 November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-118650 actively exploited?
CVE-2026-118650 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118650?
CVE-2026-118650 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-118650?
A fix for CVE-2026-118650 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118650 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-118650

Explore →

Is Your Infrastructure Affected by CVE-2026-118650?

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