Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Netty is a network application framework for development of protocol servers and clients. Prior to versions 4.1.135.Final and 4.2.15.Final, Netty's DnsResolveContext fails to validate the origin (bailiwick) of CNAME records in DNS responses. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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

Check the vendor advisory for the affected versions of 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.netty:netty-resolver-dns を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade io.netty:netty-resolver-dns to 4.1.135.Final

    ステージング環境で 4.1.135.Final に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven io.netty:netty-resolver-dns
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.135.Final"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details