Vulnerability in io.netty:netty-codec-http (CVE-2026-59898)
Summary
Vulnerability in io.netty:netty-codec-http (CVE-2026-59898). Data can be tampered with by attackers. Mitigation: upgrade to 4.1.136.Final or later.
Original description
The description as published by the source.
Summary
An attacker can force WebSocket upgrade via the lax V07 (or V08) handshaker by sending Sec-WebSocket-Version: 7 and omitting Connection: Upgrade / Upgrade: websocket headers, completing a protocol switch that a proxy would not recognize as an Upgrade request and enabling HTTP request smuggling / protocol-confusion attacks.
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-59898 has been found in io.netty:netty-codec-http.
Data can be tampered with by attackers. 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-59898" on the vendor's site.
CVE-2026-59898 (io.netty:netty-codec-http) — CWE-444 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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-444) exists in io.netty:netty-codec-http.
Check the vendor advisory for the affected versions of io.netty:netty-codec-http.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
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 でアラート再発が無いか継続監視。