Skip to main content

http4k CVE-2026-53659

| EUVDEUVD-2026-77694 HIGH
Improper Handling of Highly Compressed Data (Data Amplification) (CWE-409)
2026-08-17 https://github.com/http4k/http4k GHSA-g4w2-6h2r-3m3w
7.5
CVSS 3.1 · Vendor: https://github.com/http4k/http4k
Share

Severity by source

Vendor (https://github.com/http4k/http4k) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
7.5 HIGH

Network-reachable, no credentials needed, no interaction; impact is availability-only as heap exhaustion causes DoS with no data exposure.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/http4k/http4k).

CVSS VectorVendor: https://github.com/http4k/http4k

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
Source Code Evidence Fetched
Aug 17, 2026 - 22:21 vuln.today
Analysis Generated
Aug 17, 2026 - 22:21 vuln.today
CVE Published
Aug 17, 2026 - 21:52 github-advisory
HIGH 7.5

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 177 maven packages depend on org.http4k:http4k-core (144 direct, 33 indirect)

Ecosystem-wide dependent count for version 6.0.0.0.

DescriptionCVE.org

Impact

ServerFilters.GZip and RequestFilters.GunZip (and the underlying Gzip functions used to decompress request bodies) did not impose any cap on the decompressed size. A small malicious gzip-encoded request body (on the order of kilobytes) could decompress to gigabytes, exhausting the JVM heap and denying service to other clients.

Who is affected: any http4k server that accepts gzip-encoded requests via ServerFilters.GZip or RequestFilters.GunZip. Exploitable by any unauthenticated client. The vulnerability was introduced on 2017-08-01 (commit 2618fe08f9) and was present for ~9 years.

Patches

LineFixed inEdition
v6.x (Community)6.49.0.0Community
v5.x (LTS)5.42.0.0Enterprise - contact [enterprise@http4k.org](mailto:enterprise@http4k.org)
v4.x (LTS)4.51.0.0Enterprise - contact [enterprise@http4k.org](mailto:enterprise@http4k.org)

The fix caps decompression at 10MB by default; oversized requests through ServerFilters.GZip / RequestFilters.GunZip now return 413 Request Entity Too Large, and decompressing elsewhere throws SizeLimitExceededException. The keyed hmacSHA256 helper and other safe paths are unaffected.

Workarounds

For deployments that cannot upgrade immediately:

  • Replace the GZip / GunZip filters with custom versions that wrap the decompressed InputStream in a size-limited reader, or
  • Strip gzip-encoded request support at the edge (CDN, reverse proxy, or load balancer).

References

AnalysisAI

Unbounded gzip decompression in http4k's ServerFilters.GZip and RequestFilters.GunZip filters allows any unauthenticated remote client to exhaust JVM heap memory by sending a small (kilobyte-scale) gzip-encoded request body that decompresses to gigabytes - a classic compression bomb attack. All http4k servers using these filters across the v4.x, v5.x, and v6.x lines are affected; the flaw was silently present for approximately 9 years (since commit 2618fe08f9, 2017-08-01). …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitation requires that the http4k server has registered `ServerFilters.GZip` or `RequestFilters.GunZip` as part of its filter chain - this is a deliberate, opt-in configuration by the application developer, not a default behavior of the framework. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) accurately reflects a high-availability, low-complexity, unauthenticated network attack with no scope change or confidentiality/integrity impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation The primary fix is upgrading `org.http4k:http4k-core` to version 6.49.0.0 (Community, v6.x line), 5.42.0.0 (Enterprise LTS v5.x), or 4.51.0.0 (Enterprise LTS v4.x - confirm availability with enterprise@http4k.org, as package metadata lists this as unfixed). … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours: audit all servers and containerized deployments running http4k versions 4.x, 5.x, or 6.x, specifically identifying services with ServerFilters.GZip or RequestFilters.GunZip filters enabled. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-53659 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy