Security fix · GHSA-h7wr-284f-5qvc
Echo: Decompress permits unbounded gzip expansion in v4
Published Oct 23, 2026 · catalog updated Oct 23, 2026 · Echo: Decompress permits unbounded
Last checked Oct 27, 2026, 12 days ago.
Open the advisory
Exploitation likelihood is not on this record for GHSA-h7wr-284f-5qvc. A missing EPSS score is not a low risk. Compare Echo: Decompress permits unbounded with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Echo: Decompress permits unbounded).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- High—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Advisory link
- Affected products
- Go github.com/labstack/echo/v4
## Impact Echo v4's opt-in Decompress middleware exposed a gzip-decoded request stream without limiting its expanded size. A small compressed request could therefore produce a very large decoded body. Handlers that read or bind that body could consume excessive memory or CPU, and repeated or concurrent requests could cause denial of service. The middleware is not enabled by default. A limit on the compressed request size alone does not bound the decompressed size. Applications that already apply an effective body limit after decompression have reduced exposure. ## Affected versions and patch Echo v4 versions through v4.16.0 are affected. Upgrade to [v4.16.1](https://github.com/labstack/echo/releases/tag/v4.16.1). The patch adds , defaulting to 100 MiB when zero. A value of explicitly disables the limit. Reading beyond the cap returns (HTTP 413), including through JSON and XML binding. Bodies exactly at the configured limit remain valid. Streaming enforcement requires callers to handle body-read errors. [Fix commit](https://github.com/labstack/echo/commit/3fb0ba7e17645bb65611e2a08875d0a2f65c421f). ## Workarounds Disable gzip request decompression on exposed routes, or place BodyLimit after Decompress so the application limit applies to decoded bytes. Apply suitable request deadlines and concurrency limits as well. ## Credits Reported by @q490107865. The exact-limit behavior incorporates @Shubham-Padkonde's work in [#3136](https://github.com/labstack/echo/pull/3136).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Go github.com/labstack/echo/v44.0.0 → 4.16.1
How to fix GHSA-h7wr-284f-5qvc
Upgrade
GHSA-h7wr-284f-5qvc lists a fix boundary at 4.16.1. Compare the installed build with that boundary before you change production.
Version check
Seen in 4.0.0 → 4.16.1
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for GHSA-h7wr-284f-5qvc. A missing EPSS score is not a low risk. Compare Echo: Decompress permits unbounded with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 4.0.0 → 4.16.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-400: Uncontrolled Resource Consumption; CWE-409. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 23, 2026 · Go Vulnerability Database
Detected
## Impact Echo v4's opt-in Decompress middleware exposed a gzip-decoded request stream without limiting its expanded size. A small compressed request could therefore produce a very large decoded body. Handlers that read or bind that body could consume excessive memory or CPU, and repeated or concurrent requests could cause denial of service. The middleware is not enabled by default. A limit on the
Oct 23, 2026 · Go Vulnerability Database
Fix available
github.com/labstack/echo/v4 fixed in 4.16.1
Oct 23, 2026 · Go Vulnerability Database
Fix available
github.com/labstack/echo/v4 fixed in 4.16.1
Oct 23, 2026 · Go Vulnerability Database
Updated
## Impact Echo v4's opt-in Decompress middleware exposed a gzip-decoded request stream without limiting its expanded size. A small compressed request could therefore produce a very large decoded body. Handlers that read or bind that body could consume excessive memory or CPU, and repeated or concurrent requests could cause denial of service. The middleware is not enabled by default. A limit on the
Sources
- Go Vulnerability DatabasePackage advisoryGHSA-h7wr-284f-5qvc
Echo: Decompress permits unbounded gzip expansion in v4
osv.dev
References
Freshness
Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- Go Vulnerability DatabaseOct 27, 2026