← Back
CVE-2026-45674
high
CVSS 8.7
Vulnerability in io.netty:netty-resolver-dns (CVE-2026-45674)
Summary
vulnerability in io.netty:netty-resolver-dns (CVE-2026-45674). Confidential information can be exposed externally. Mitigation: upgrade to `4.1.135.Final` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45674** has been found in io.netty:netty-resolver-dns.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade io.netty:netty-resolver-dns to **4.1.135.Final** or later.
If unsure, ask your IT team or search "io.netty:netty-resolver-dns CVE-2026-45674" on the vendor's site.
CVE-2026-45674 (io.netty:netty-resolver-dns) — CWE-345 / CVSS v3 8.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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-345) exists in io.netty:netty-resolver-dns.
📍 Affected scope
io.netty:netty-resolver-dns — .
🔥 Severity
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally
🔧 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-resolver-dns' .` 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-resolver-dns' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.netty:netty-resolver-dns` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.netty:netty-resolver-dns 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-resolver-dns
[{"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-676x-f7gg-47vc
- 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-676x-f7gg-47vc
- web https://nvd.nist.gov/vuln/detail/CVE-2026-45674
- 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-45674
- web https://bugzilla.redhat.com/show_bug.cgi?id=2488400
- web https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45674.json
- web https://access.redhat.com/errata/RHSA-2026:34608