Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

High severity, with a CVSS score of 4, published 23 October 2026.

Which products and versions are affected?

github.com/labstack/echo/v4 (Go) >= 4.0.0, < 4.16.1, SEMVER:introduced=4.0.0,fixed=4.16.1; Labstack Echo 4.0.0 through 4.16.0, v4.0 through v4.16.0.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run github.com/labstack/echo/v4 (Go) or Labstack Echo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Echo BodyDump unbounded memory allocation denial of service

Q: Is there a fix for This vulnerability?

Yes. github.com/labstack/echo/v4 (Go): upgrade to 4.16.1 or later. Until then: Disable BodyDump on exposed routes, particularly those handling large uploads or downloads. Alternatively, enforce body-size limits before BodyDump is applied and independently bound the responses that the application generates. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a software library.

Q: Am I affected?

Check whether you run github.com/labstack/echo/v4 (Go) or Labstack Echo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Severity: high · CVSS 4 · Published 2026-10-23

Echo is a Go web framework, and its optional BodyDump middleware captures HTTP request and response bodies for logging and debugging. When enabled, BodyDump allocates unbounded memory to store complete request and response bodies, allowing an attacker to send large requests or generate large responses to exhaust server memory and cause a denial-of-service outage. Because BodyDump is not enabled by default, only applications that explicitly enable it are affected.

Technologies: github.com/labstack/echo/v4 (Go), Labstack Echo. Vendors: Go, Labstack.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: High severity, with a CVSS score of 4, published 23 October 2026.
Which products and versions are affected?: github.com/labstack/echo/v4 (Go) >= 4.0.0, < 4.16.1, SEMVER:introduced=4.0.0,fixed=4.16.1; Labstack Echo 4.0.0 through 4.16.0, v4.0 through v4.16.0.
Is there a fix for This vulnerability?: Yes. github.com/labstack/echo/v4 (Go): upgrade to 4.16.1 or later. Until then: Disable BodyDump on exposed routes, particularly those handling large uploads or downloads. Alternatively, enforce body-size limits before BodyDump is applied and independently bound the responses that the application generates. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run github.com/labstack/echo/v4 (Go) or Labstack Echo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/labstack/echo/v4 (Go): upgrade to 4.16.1 or later
```
go get github.com/labstack/echo/v4@v4.16.1
```

Disable BodyDump on exposed routes, particularly those handling large uploads or downloads. Alternatively, enforce body-size limits before BodyDump is applied and independently bound the responses that the application generates.

Technical details

The BodyDump middleware in Echo v4 reads complete request bodies and response bodies into memory without size limits (CWE-400, CWE-770). An attacker can submit large requests to routes with BodyDump enabled, or trigger large response generation, causing unbounded memory allocation. Repeated or concurrent requests exhaust process memory. The fix adds MaxRequestBytes and MaxResponseBytes configuration options, each defaulting to 5 MiB, while preserving the complete request and response to the handler and client respectively.

Affected products

labstack Echo 4.0.0 through 4.16.0

Timeline

2026-10-23: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.