Vulnerability in io.netty:netty-codec-http (CVE-2026-41417)
Summary
Vulnerability in io.netty:netty-codec-http (CVE-2026-41417). Risk of unauthorized operations or information disclosure. Exploitable via POST /s2. Mitigation: upgrade to 4.2.13.Final or later.
Original description
The description as published by the source.
Netty allows request-line validation to be bypassed when a DefaultHttpRequest or DefaultFullHttpRequest is created first and its URI is later changed via setUri(). The constructors reject CRLF and whitespace characters that would break the start-line, but setUri() does not apply the same validation. HttpRequestEncoder and RtspEncoder then write the URI into the request line verbatim. If attacker-controlled input reaches setUri(), this enables CRLF injection and insertion of additional HTTP or RTSP requests, leading to HTTP request smuggling or desynchronization on the HTTP side and request injection on the RTSP side. This issue is fixed in versions 4.2.13.Final and 4.1.133.Final.
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-41417 has been found in io.netty:netty-codec-http.
Attackers can target a specific entry point like POST /s2 over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade io.netty:netty-codec-http to 4.2.13.Final or later.
If unsure, ask your IT team or search "io.netty:netty-codec-http CVE-2026-41417" on the vendor's site.
CVE-2026-41417 (io.netty:netty-codec-http) — CWE-444 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /s2 / GET /s1 / DefaultHttpRequest / DefaultFullHttpRequest
Patched: 4.2.13.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. Attackers reach the vulnerable code path via POST /s2 without authentication.
Check the vendor advisory for the affected versions of io.netty:netty-codec-http. Attack surface: POST /s2 / GET /s1 / DefaultHttpRequest / DefaultFullHttpRequest.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 4.2.13.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 POST /s2 requests with malformed payloads or SQL meta-characters. 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 を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /s2' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /s2への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade io.netty:netty-codec-http to 4.2.13.Finalステージング環境で 4.2.13.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /s2 on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-41417 netty
- Ubuntu UBUNTU-CVE-2026-41417 netty
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com