CVE-2026-55677

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th 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
Trending — 3 sources updated this weekElevated
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.15.3 and 5.2.0, Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization. This vulnerability is fixed in 4.15.3 and 5.2.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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.
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
35th
KEV
Not listed

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.

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

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Encoded slash (%2F) bypasses route-level protection and exposes static files · Advisory · labstack/echo · GitHub

https://github.com/labstack/echo/security/advisories/GHSA-vfp3-v2gw-7wfq

Vendor Advisories for CVE-2026-55677(15)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatosbuild-composer-0:165.1-5.el9_82026-09-21redhat
redhatosbuild-composer-0:101.5-3.el8_102026-09-14redhat
redhatosbuild-composer-0:165.1-5.el10_22026-09-11redhat
redhatosbuild-composer-0:134.1-10.el10_02026-09-03redhat
redhatosbuild-composer-0:76.1-8.el9_22026-08-31redhat
redhatcluster-observability-operator/perses-rhel9-operator:17875936972026-08-31redhat
redhatrhacm2/acm-multicluster-observability-addon-rhel9:17873148162026-08-26redhat
redhatrhacm2/acm-multicluster-observability-addon-rhel9:17873148132026-08-26redhat
redhatrhacm2/acm-multicluster-observability-addon-rhel9:17873148182026-08-26redhat
redhatosbuild-composer-0:132.2-10.el9_62026-08-20redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17854428722026-08-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17854436572026-08-10redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17849066282026-07-28redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat

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

(7 across 5 ecosystems)
Go(3)
PackageVulnerable rangeFix by version rangeDependents
github.com/labstack/echo—
  • every version through 3.3.10: no fix on record
—
github.com/labstack/echo/v4—
  • every version up to 4.15.3: fixed in 4.15.3
—
github.com/labstack/echo/v5—
  • every version up to 5.2.0: fixed in 5.2.0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-labstack-echo.v33.3.10-1, 3.3.10-2
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-labstack-echo4.11.1-1, 4.11.1-2, 4.12.0-1, 4.2.1-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-labstack-echo4.12.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-labstack-echo4.12.0-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 36× 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.

Showing the most recent 100 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-10-12 15:41 UTCEG score recompute
  5. 2026-10-12 15:41 UTCVendor advisory
  6. 2026-10-11 19:38 UTCEG score recompute
  7. 2026-10-11 16:54 UTCEG score recompute
  8. 2026-10-11 14:16 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-09-23 07:51 UTCEG score recompute
  3. 2026-09-23 07:51 UTCVendor advisory
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-09-18 07:13 UTCEG score recompute
  7. 2026-09-18 07:13 UTCVendor advisory
  8. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-09-14 01:10 UTCEG score recompute
  13. 2026-09-14 01:10 UTCVendor advisory
  14. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-09-13 09:32 UTCVendor advisory
  16. 2026-09-12 15:34 UTCEG score recompute
  17. 2026-09-12 15:34 UTCVendor advisory
  18. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  27. 2026-08-30 19:21 UTCEG score recompute
  28. 2026-08-30 19:21 UTCVendor advisory
  29. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  31. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-08-27 23:04 UTCEG score recompute
  33. 2026-08-27 23:04 UTCVendor advisory
  34. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  35. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  37. 2026-08-25 00:22 UTCEG score recompute
  38. 2026-08-25 00:22 UTCVendor advisory
  39. 2026-08-24 12:53 UTCEG score recompute
  40. 2026-08-24 12:53 UTCVendor advisory
  41. 2026-08-23 20:00 UTCVendor advisory
  42. 2026-08-23 08:32 UTCEG score recompute
  43. 2026-08-23 08:32 UTCVendor advisory
  44. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  45. 2026-08-22 21:03 UTCVendor advisory
  46. 2026-08-22 09:32 UTCEG score recompute
  47. 2026-08-22 09:32 UTCVendor advisory
  48. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  49. 2026-08-21 17:23 UTCVendor advisory
  50. 2026-08-21 05:48 UTCEG score recompute
  51. 2026-08-21 05:48 UTCVendor advisory
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  53. 2026-08-20 18:19 UTCVendor advisory
  54. 2026-08-20 06:50 UTCEG score recompute
  55. 2026-08-20 06:50 UTCVendor advisory
  56. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  57. 2026-08-19 12:37 UTCVendor advisory
  58. 2026-08-18 23:55 UTCEG score recompute
  59. 2026-08-18 23:55 UTCVendor advisory
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  61. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-17 07:28 UTCVendor advisory
  63. 2026-08-16 20:01 UTCEG score recompute
  64. 2026-08-16 20:01 UTCVendor advisory
  65. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  66. 2026-08-16 08:00 UTCEG score recompute
  67. 2026-08-16 08:00 UTCVendor advisory
  68. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  69. 2026-08-15 20:33 UTCVendor advisory
  70. 2026-08-15 09:05 UTCEG score recompute
  71. 2026-08-15 09:05 UTCVendor advisory
  72. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  73. 2026-08-14 21:37 UTCVendor advisory
  74. 2026-08-14 10:10 UTCVendor advisory
  75. 2026-08-13 22:42 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same product

3 shown

Debian:12:golang-github-labstack-echo · Go:github.com/labstack/echo/v5 · Go:github.com/labstack/echo/v4

Frequently asked(5)

What is CVE-2026-55677?
CVE-2026-55677 is a high-severity vulnerability; its CVE record was published on June 26, 2026. Echo is a Go web framework. Prior to 4.15.3 and 5.2.0, Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an…
When was the CVE record for CVE-2026-55677 published?
The CVE record for CVE-2026-55677 was published on June 26, 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 June 26, 2026; the record at its source may have been updated since.
Is CVE-2026-55677 actively exploited?
CVE-2026-55677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55677?
CVE-2026-55677 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-55677?
A fix for CVE-2026-55677 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55677 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-55677

Explore →

Is Your Infrastructure Affected by CVE-2026-55677?

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

Book a Demo →Browse All CVEs