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

Advisory record · `GHSA-x9ff-22gv-65f4`

- **Identifiers:** `GHSA-x9ff-22gv-65f4` · `CVE-2026-118263` · `GO-2026-6844`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-252](https://cwe.mitre.org/data/definitions/252.html)
- **Tags:** [CWE-252](https://agentprime.io/advisories/tag/cwe-252.md)
- **Published:** 23 Oct 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Oct 2026, 20:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/labstack/echo/v5` (Go): affected `>=5.0.0, <5.4.1`; fixed in `5.4.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Echo v5 (github.com/labstack/echo/v5) versions 5.0.0 through 5.4.0 are affected. When the BodyDump middleware runs behind a BodyLimit, an unknown-length request such as a chunked HTTP/1.1 request can exceed the configured limit without an error, so the handler processes a truncated body and returns success. Upgrade to v5.4.1. As a workaround, disable BodyDump on affected routes or set its capture limit above the BodyLimit.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.3 Medium, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 32nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 28 Oct 2026, 19:01 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-118263)
- 28 Oct 2026, 19:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-118263)
- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x9ff-22gv-65f4)

## Sources

- [GitHub Advisory Database: GHSA-x9ff-22gv-65f4](https://github.com/advisories/GHSA-x9ff-22gv-65f4)
- [OSV: GHSA-x9ff-22gv-65f4](https://osv.dev/vulnerability/GHSA-x9ff-22gv-65f4)
- <https://github.com/labstack/echo/security/advisories/GHSA-x9ff-22gv-65f4>
- <https://github.com/labstack/echo/pull/3105>
- <https://github.com/labstack/echo/commit/1855061e572ae9dab727c811d8382f266bfbaaec>
- <https://github.com/labstack/echo>
- <https://github.com/labstack/echo/releases/tag/v5.4.1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x9ff-22gv-65f4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x9ff-22gv-65f4/>. Everything for agents: <https://agentprime.io/llms.txt>.