Vulnerability in io.netty:netty-codec-http (CVE-2026-59899)
Summary
Vulnerability in io.netty:netty-codec-http (CVE-2026-59899). Risk of unauthorized operations or information disclosure. Exploitable via HttpContentEncoder. Mitigation: upgrade to 4.1.136.Final or later.
Original description
The description as published by the source.
Impact
HttpContentEncoder (the superclass of the production handler HttpContentCompressor) maintains a per-channel ArrayDeque named acceptEncodingQueue that accumulates attacker-controlled data without any size limit. The queue is filled on the I/O thread for every inbound HTTP request and drained only when the application later writes a non-1xx response. This creates a resource exhaustion vulnerability when an attacker exploits HTTP/1.1 pipelining to flood the connection with requests faster than the application produces responses.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59899 has been found in io.netty:netty-codec-http.
Attackers can target a specific entry point like HttpContentEncoder over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade io.netty:netty-codec-http to 4.1.136.Final or later.
If unsure, ask your IT team or search "io.netty:netty-codec-http CVE-2026-59899" on the vendor's site.
CVE-2026-59899 (io.netty:netty-codec-http) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: HttpContentEncoder / HttpContentCompressor / acceptEncodingQueue
Patched: 4.1.136.Final — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in io.netty:netty-codec-http. Attackers reach the vulnerable code path via HttpContentEncoder without authentication.
Check the vendor advisory for the affected versions of io.netty:netty-codec-http. Attack surface: HttpContentEncoder / HttpContentCompressor / acceptEncodingQueue.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 4.1.136.Final.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.netty:netty-codec-http を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.netty:netty-codec-http to 4.1.136.Finalステージング環境で 4.1.136.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。