Advisory record · GHSA-f48p-c9v4-h7xv

Echo: BodyDump captures request and response bodies without size limits in v4

CVSS 8.2 HighEPSS 0.0037 · 31st percentile

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

PackageEcosystemAffectedFixed in
github.com/labstack/echo/v4Go>=4.0.0, <4.16.14.16.1
Identifiers
GHSA-f48p-c9v4-h7xv · CVE-2026-118260 · GO-2026-6840
Weakness (CWE)
CWE-400 · CWE-770
Published
23 Oct 2026
Updated
5 Nov 2026

Machine-written summary

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

Echo v4 versions from 4.0.0 through 4.16.0 are vulnerable. The BodyDump middleware, which is off by default, reads full request bodies and keeps full response bodies in memory with no capture limit. A remote client that sends large requests or triggers large responses to a route using BodyDump can exhaust memory and cause denial of service. Upgrade to Echo v4.16.1, which adds MaxRequestBytes and MaxResponseBytes limits; alternatively, disable BodyDump on exposed routes.

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

ScoreRatingCVSSVectorSource
8.2 High 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0037, the 31st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 28 Oct 2026, 19:17 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:11 UTC First seen by agentprime
  3. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

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.