CVE-2026-118261

Echo: Decompress permits unbounded gzip expansion in v4

Published Oct 28, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
Echo is a Go web framework. From 4.0.0 until 4.16.1, Echo v4's opt-in Decompress middleware exposes a gzip-decoded request stream without limiting its expanded size. A small compressed request can expand into a very large body when a handler reads or binds it, consuming excessive memory or CPU and allowing repeated or concurrent requests to cause denial of service. The middleware is not enabled by default, and limiting only the compressed request size does not bound the decoded size. This issue is fixed in 4.16.1.

Analysis

AI-generated

Technical impact

Echo’s opt‑in Decompress middleware allows a gzip‑compressed request to expand without any upper bound. A small compressed payload can grow into a massive body when parsed by a handler, consuming excessive memory or CPU. This uncontrolled resource consumption can lead to application slowdown or crash, directly resulting in denial of service.

Affected Systems

The vulnerability exists in labstack Echo version 4.0.0 through 4.16.1. Any deployment of Echo v4 within that range that has the Decompress middleware enabled is susceptible.

Risk and Exploitability

The CVSS score of 8.2 indicates a high severity, yet the EPSS score is unavailable, making it unclear how frequently this flaw is targeted. The flaw is not catalogued in CISA KEV. An attacker can trigger the issue by sending a specially crafted HTTP request bearing a gzip Content‑Encoding header and a compressed body that, once decompressed, exceeds normal limits. Because the middleware is opt‑in, a vulnerable system must have it enabled for exploitation to succeed; disabling the middleware eliminates the risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to Echo 4.16.1 or later where the issue is fixed
  • If an update is not immediately feasible, ensure the Decompress middleware is disabled or removed from the request pipeline
  • Implement application‑level monitoring for memory or CPU spikes and employ rate limiting or other mitigations to reduce the impact of a potential denial of service attempt

Generated by OpenCVE AI on October 28, 2026 at 20:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-h7wr-284f-5qvc Echo: Decompress permits unbounded gzip expansion in v4
History
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Labstack
Labstack echo
Vendors & Products Labstack
Labstack echo
Type Values Removed Values Added
Description Echo is a Go web framework. From 4.0.0 until 4.16.1, Echo v4's opt-in Decompress middleware exposes a gzip-decoded request stream without limiting its expanded size. A small compressed request can expand into a very large body when a handler reads or binds it, consuming excessive memory or CPU and allowing repeated or concurrent requests to cause denial of service. The middleware is not enabled by default, and limiting only the compressed request size does not bound the decoded size. This issue is fixed in 4.16.1.
Title Echo: Decompress permits unbounded gzip expansion in v4
Weaknesses CWE-400
CWE-409
References
Metrics cvssV4_0

{'score': 8.2, 'vector': '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'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-409

    Improper Handling of Highly Compressed Data (Data Amplification)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 29, 2026, 8:54 PM
Reserved
Oct 27, 2026, 8:13 PM
Status
Undergoing Analysis
Published
Oct 28, 2026, 7:17 PM
Modified
Nov 4, 2026, 11:10 PM
Severity
Important
Public date
Oct 28, 2026, 6:58 PM