← Back
CVE-2026-48480
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.
AI summary snake-internal / snake-material-v2
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. CVSS score: ?/10.
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.
❓ What is the problem
**A vulnerability** (CWE-325) exists in io.netty.incubator:netty-incubator-codec-ohttp.
📍 Affected scope
io.netty.incubator:netty-incubator-codec-ohttp — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.22.Final**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.netty.incubator:netty-incubator-codec-ohttp' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'io.netty.incubator:netty-incubator-codec-ohttp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.netty.incubator:netty-incubator-codec-ohttp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.netty.incubator:netty-incubator-codec-ohttp to 0.0.22.Finalステージング環境で 0.0.22.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.netty.incubator:netty-incubator-codec-ohttp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.22.Final"}]}]
References
- web https://github.com/netty/netty-incubator-codec-ohttp/commit/28f977f293591a4e837bd59ceb441f9f70349915
- web https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-r6fj-869h-4f6q
- web https://nvd.nist.gov/vuln/detail/CVE-2026-48480
- web https://github.com/advisories/GHSA-r6fj-869h-4f6q