← Back
CVE-2026-45673
medium
CVSS 6.8
Vulnerability in io.netty:netty-resolver-dns (CVE-2026-45673)
Summary
vulnerability in io.netty:netty-resolver-dns (CVE-2026-45673). Data can be tampered with by attackers. Exploitable via ``DnsQueryIdSpace``. Mitigation: upgrade to `4.1.135.Final` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45673** has been found in io.netty:netty-resolver-dns.
Attackers can target a specific entry point like ``DnsQueryIdSpace`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.8/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-45673" on the vendor's site.
CVE-2026-45673 (io.netty:netty-resolver-dns) — CWE-330 / CVSS v3 6.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `DnsQueryIdSpace` / `DnsNameResolverBuilder` / `channelStrategy` / `ChannelPerResolver`
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-330) exists in io.netty:netty-resolver-dns. Attackers reach the vulnerable code path via ``DnsQueryIdSpace`` without authentication.
📍 Affected scope
io.netty:netty-resolver-dns — . Attack surface: `DnsQueryIdSpace` / `DnsNameResolverBuilder` / `channelStrategy` / `ChannelPerResolver`.
🔥 Severity
Severity: Medium (CVSS 6.8/10). Data can be tampered with by attackers
🔧 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
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45673
- package https://github.com/netty/netty
- web https://github.com/netty/netty/security/advisories/GHSA-xmv7-r254-6q78
- 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-xmv7-r254-6q78