cve.bz

CVE-2026-118261 labstack echo: Uncontrolled Resource Consumption

8.2 highEPSS 0.4%Fix available

High (8.2) in labstack echo. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/labstack/echo/v4 4.16.1.

On this page
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.

Severity

CVSS 4.0

8.2 high
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
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/labstack/echo/v4 (Go): fixed in 4.16.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-118261 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118261?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118261?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118261 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
labstack echo>= 4.0.0, < 4.16.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h7wr-284f-5qvcGogithub.com/labstack/echo/v4>=4.0.0 <4.16.14.16.1
GO-2026-6842Gogithub.com/labstack/echo/v4>=4.0.0 <4.16.14.16.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-labstack-echono fix listedDEBIAN-CVE-2026-118261
Ubuntu20.04:LTSgolang-github-labstack-echo.v2, golang-github-labstack-echo.v3no fix listedUBUNTU-CVE-2026-118261
Ubuntu22.04:LTSgolang-github-labstack-echo, golang-github-labstack-echo.v2, golang-github-labstack-echo.v3no fix listedUBUNTU-CVE-2026-118261
Ubuntu24.04:LTS, 26.04:LTS, 26.10golang-github-labstack-echono fix listedUBUNTU-CVE-2026-118261

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON