# CVE-2026-118263: Echo: BodyDump can discard BodyLimit overflow errors for unknown-length requests


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** ECHO-89c4-2f2d-3bfb, GHSA-x9ff-22gv-65f4, UBUNTU-CVE-2026-118263

## What is CVE-2026-118263?

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

### Official description

Echo is a Go web framework. From 5.0.0 until 5.4.1, Echo v5's BodyDump middleware can discard a BodyLimit overflow error for an unknown-length request when BodyDump's capture limit is below the BodyLimit threshold. BodyDump drains the remaining body while ignoring read errors and replaces it with the captured prefix, so an HTTP/1.1 chunked request can be truncated and processed successfully even though the original body exceeded the configured limit. Known-length requests rejected before BodyDump runs are unaffected, and the issue does not establish a general authentication bypass or denial of service. This issue is fixed in 5.4.1.

Weakness: CWE-252 (Unchecked Return Value)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/labstack/echo/v5` | Go | From 5.0.0 | 5.4.1 |
| `github.com/labstack/echo/v5` | Go | From 5.0.0 | 5.4.1 |

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

Upgrade github.com/labstack/echo/v5 to 5.4.1 or later.

## Is CVE-2026-118263 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- github.com/labstack/echo/v5 (Go): affected from 5.0.0; fixed in 5.4.1
- github.com/labstack/echo/v5 (Go): affected from 5.0.0; fixed in 5.4.1

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-118263/ (Markdown: https://insights.sbomify.com/CVE-2026-118263/index.md)
```

## Sources

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

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