CVE-2026-55677

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

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(9)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/acm-multicluster-observability-addon-rhel9:17873148162026-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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-github-labstack-echo.v33.3.10-1, 3.3.10-2——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-labstack-echo4.11.1-1, 4.11.1-2, 4.12.0-1, 4.2.1-3——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-labstack-echo4.12.0-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-labstack-echo4.12.0-1——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 99× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 163 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55677?
CVE-2026-55677 is a high vulnerability 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 CVE-2026-55677 disclosed?
CVE-2026-55677 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55677 actively exploited?
CVE-2026-55677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.2% of all scored CVEs.
What is the CVSS score of CVE-2026-55677?
CVE-2026-55677 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-55677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55677, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs