# CVE-2026-118650: Echo: middleware.Static: `%2F`-encoded path bypasses route/group middleware guarding a statically-served path


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** ECHO-11f4-8fd8-558e, GHSA-375p-5qhx-8wq4, UBUNTU-CVE-2026-118650

## What is CVE-2026-118650?

CVE-2026-118650 is a high-severity vulnerability in labstack echo, published on 28 Oct 2026. 

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization), CWE-177 (Improper Handling of URL Encoding (Hex Encoding))

## Which versions are affected by CVE-2026-118650?

4 open source packages ship an affected version, including github.com/labstack/echo/v4 and github.com/labstack/echo/v5.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/labstack/echo/v4` | Go | All versions | 4.16.0 |
| `github.com/labstack/echo/v4` | Go | All versions | 4.16.0 |
| `github.com/labstack/echo/v5` | Go | All versions | 5.4.0 |
| `github.com/labstack/echo/v5` | Go | All versions | 5.4.0 |

## How do I fix CVE-2026-118650?

Upgrade github.com/labstack/echo/v4 to 4.16.0 or later.

## Is CVE-2026-118650 being exploited?

There is no known exploitation of CVE-2026-118650 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118650 and fix it if it is affected.

What it is: CVE-2026-118650 is a high-severity vulnerability in labstack echo, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118650 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.16.0
- github.com/labstack/echo/v4 (Go): affected all versions; fixed in 4.16.0
- github.com/labstack/echo/v5 (Go): affected all versions; fixed in 5.4.0
- github.com/labstack/echo/v5 (Go): affected all versions; fixed in 5.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118650/ (Markdown: https://insights.sbomify.com/CVE-2026-118650/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118650
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118650
- OSV: https://osv.dev/vulnerability/CVE-2026-118650

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118650/
Summaries are generated and may contain mistakes; the official description above is the record.