Skip to main content
VulnerabilityPublished Updated

CVE-2026-118261: Echo · Decompress permits unbounded gzip expansion in v4

Affects github.com/labstack/echo/v4Source GCVE Database

0
Authoritative record:CVE-2026-118261· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 4.16.1 soon.

Data as of 28 Oct 2026, 20:14 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.16.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade github.com/labstack/echo/v4 to 4.16.1.

Affected software

ProductAffectedFixed in
Gogithub.com/labstack/echo/v4Affected
  • >=4.0.0 <4.16.1
Fixed in
  • 4.16.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Echo v4 to version 4.16.1 or later, which includes a fix adding a configurable maximum decompressed size limit (MaxDecompressedSize) defaulting to 100 MiB. Alternatively, disable gzip request decompression on exposed routes or ensure that a BodyLimit middleware is applied after Decompress to limit the decompressed body size. Also, apply appropriate request deadlines and concurrency limits to reduce risk.

Description

Echo v4's optional Decompress middleware for gzip requests allowed unbounded decompression size, enabling a small compressed request to expand into a very large body. This could cause excessive memory or CPU consumption, leading to denial of service. The middleware is not enabled by default. Versions prior to 4.16.1 are affected. The issue is fixed in Echo v4.16.1 by adding a configurable maximum decompressed size limit.

References

Community reviews

Loading reviews…