← Back
CVE-2026-48059
high
CVSS 7.5
Vulnerability in io.netty:netty-codec-haproxy (CVE-2026-48059)
Summary
vulnerability in io.netty:netty-codec-haproxy (CVE-2026-48059). Risk of unauthorized operations or information disclosure. Exploitable via ``PP2_TYPE_SSL``. Mitigation: upgrade to `4.1.135.Final` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48059** has been found in io.netty:netty-codec-haproxy.
Attackers can target a specific entry point like ``PP2_TYPE_SSL`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade io.netty:netty-codec-haproxy to **4.1.135.Final** or later.
If unsure, ask your IT team or search "io.netty:netty-codec-haproxy CVE-2026-48059" on the vendor's site.
CVE-2026-48059 (io.netty:netty-codec-haproxy) — CWE-401 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `PP2_TYPE_SSL` / `HAProxyMessage` / `ByteBuf`
Patched: `4.1.135.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-401) exists in io.netty:netty-codec-haproxy. Attackers reach the vulnerable code path via ``PP2_TYPE_SSL`` without authentication.
📍 Affected scope
io.netty:netty-codec-haproxy — . Attack surface: `PP2_TYPE_SSL` / `HAProxyMessage` / `ByteBuf`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.1.135.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-codec-haproxy' .` 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-codec-haproxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.netty:netty-codec-haproxy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.netty:netty-codec-haproxy to 4.1.135.Finalステージング環境で 4.1.135.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.netty:netty-codec-haproxy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.135.Final"}]}]
References
- package https://github.com/netty/netty
- web https://github.com/netty/netty/security/advisories/GHSA-h2qv-fj59-j46j
- web https://github.com/netty/netty/releases/tag/netty-4.1.135.Final
- web https://github.com/netty/netty/releases/tag/netty-4.2.15.Final
- web https://github.com/advisories/GHSA-h2qv-fj59-j46j
- web https://nvd.nist.gov/vuln/detail/CVE-2026-48059
- web https://access.redhat.com/errata/RHSA-2026:26017
- web https://access.redhat.com/errata/RHSA-2026:26018
- web https://access.redhat.com/errata/RHSA-2026:26586
- web https://access.redhat.com/security/cve/CVE-2026-48059
- web https://bugzilla.redhat.com/show_bug.cgi?id=2488437
- web https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-48059.json
- web https://access.redhat.com/errata/RHSA-2026:34608