← Back
CVE-2026-42578
high
CVSS 7.5
Vulnerability in io.netty:netty-handler-proxy (CVE-2026-42578)
Summary
vulnerability in io.netty:netty-handler-proxy (CVE-2026-42578). Data can be tampered with by attackers. Exploitable via ``io.netty.handler.proxy.HttpProxyHandler``. Mitigation: upgrade to `4.2.13.Final` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42578** has been found in io.netty:netty-handler-proxy.
Attackers can target a specific entry point like ``io.netty.handler.proxy.HttpProxyHandler`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade io.netty:netty-handler-proxy to **4.2.13.Final** or later.
If unsure, ask your IT team or search "io.netty:netty-handler-proxy CVE-2026-42578" on the vendor's site.
CVE-2026-42578 (io.netty:netty-handler-proxy) — CWE-113 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `io.netty.handler.proxy.HttpProxyHandler` / `HttpProxyHandler` / `outboundHeaders` / `DefaultHttpRequest`
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.
❓ What is the problem
**A vulnerability** (CWE-113) exists in io.netty:netty-handler-proxy. Attackers reach the vulnerable code path via ``io.netty.handler.proxy.HttpProxyHandler`` without authentication.
📍 Affected scope
io.netty:netty-handler-proxy — . Attack surface: `io.netty.handler.proxy.HttpProxyHandler` / `HttpProxyHandler` / `outboundHeaders` / `DefaultHttpRequest`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **4.2.13.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:netty-handler-proxy' .` 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:netty-handler-proxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.netty:netty-handler-proxy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.netty:netty-handler-proxy to 4.2.13.Finalステージング環境で 4.2.13.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.netty:netty-handler-proxy
[{"type":"ECOSYSTEM","events":[{"introduced":"4.2.0.Alpha1"},{"fixed":"4.2.13.Final"}]}]
References
- advisory https://github.com/advisories/GHSA-84h7-rjj3-6jx4
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42578
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- package https://github.com/netty/netty
- web https://github.com/advisories/GHSA-45q3-82m4-75jr
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- web 0b0ca135-0b70-47e7-9f44-1890c2a1c46c