Vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (CVE-2026-48480)
Summary
Vulnerability in io.netty.incubator:netty-incubator-codec-ohttp (CVE-2026-48480). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.0.22.Final or later.
Original description
The description as published by the source.
The codec-ohttp implementation of draft-ietf-ohai-chunked-ohttp does not verify that a cryptographically-signed final chunk was received before the outer HTTP body terminates. An on-path adversary (the OHTTP relay itself, or any MITM on the relay↔gateway or relay↔client transport) can forward a prefix of a legitimate chunked-OHTTP message—cut at a non-final chunk boundary—and close the outer body cleanly, producing no decryption error and no exception in the receiving application.
Source: NIST National Vulnerability Database 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-48480 has been found in io.netty.incubator:netty-incubator-codec-ohttp.
Risk of unauthorized operations or information disclosure.
What to do: upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.22.Final or later.
If unsure, ask your IT team or search "io.netty.incubator:netty-incubator-codec-ohttp CVE-2026-48480" on the vendor's site.
CVE-2026-48480 (io.netty.incubator:netty-incubator-codec-ohttp) — CWE-325
Patched: 0.0.22.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-325) exists in io.netty.incubator:netty-incubator-codec-ohttp.
Check the vendor advisory for the affected versions of io.netty.incubator:netty-incubator-codec-ohttp.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.0.22.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.incubator:netty-incubator-codec-ohttp を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.22.Finalステージング環境で 0.0.22.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com