# CVE-2026-45674: Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records > Netty fails to validate CNAME record origins, allowing DNS cache poisoning attacks that bypass security controls. - **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Jun 2026 - **Updated:** 18 Sep 2026 - **Also known as:** CLEANSTART-2026-AG72812, CLEANSTART-2026-CD10863, CLEANSTART-2026-JI47500, CLEANSTART-2026-NB58291, DEBIAN-CVE-2026-45674, ECHO-b66e-8a32-1e5f, GHSA-676x-f7gg-47vc, MINI-268c-66hx-rc6h, MINI-27qw-2rj8-h7jr, MINI-2hcv-jp88-gcfr, MINI-2mqg-q633-45r5, MINI-2rj3-x5pp-p8x3, MINI-36hw-9ww4-cmmj, MINI-39m3-fm34-v2x8, MINI-3cvq-rfvw-mjgh, MINI-3f5h-q4vj-p47m, MINI-3rhf-22xg-6f2f, MINI-3xwm-v447-v276, MINI-4244-9jmv-ppfh, MINI-4hh7-75ww-j7c9, MINI-4q7c-f49j-v6gv, MINI-569m-2x4w-ff89, MINI-5rqc-f835-q9r6, MINI-5v5r-r56w-chjc, MINI-6889-2hc3-mqhx, MINI-6f79-rh62-wm53, MINI-6j3g-rxv8-h55r, MINI-76hx-2277-xp8f, MINI-7737-f527-5m9h, MINI-7f6f-jr6x-jg62, MINI-7xqv-99m6-j75h, MINI-8r33-j4ph-wfwx, MINI-9443-2qw9-855x, MINI-9g69-47fp-34x9, MINI-9rw4-vfc7-qhr4, MINI-c4g8-ph34-327x, MINI-cj99-cvhq-hrwm, MINI-cm3h-2vw5-9q2v, MINI-cqf9-hc3w-qp69, MINI-cw6v-3v5x-39vc, MINI-f2p8-x524-7866, MINI-fx7q-rcrr-2vjv, MINI-gc33-f7g4-5vqj, MINI-ggjr-pfrh-vm58, MINI-gjmv-jvwj-2cmc, MINI-gwf2-f9r5-59p2, MINI-h5r5-4qr2-pph4, MINI-jc66-v25g-cqww, MINI-jgcq-v3fj-vq2g, MINI-jh3x-4hxv-v2xr, MINI-jmm2-qcqv-89v4, MINI-jmwm-xxcr-cvjq, MINI-jpp3-vx47-5pwj, MINI-m2wr-595r-4qvw, MINI-m2x6-89p9-wj5w, MINI-mm7g-p6gh-hh6w, MINI-p37w-vg84-gcgc, MINI-p84p-w95p-wvcq, MINI-pc86-qm2h-mv39, MINI-pwpx-2h7p-vv72, MINI-q3mg-mfr7-47xw, MINI-q55h-v7p8-cwx6, MINI-qchr-4chp-ff8f, MINI-qhhh-jwqf-9gjq, MINI-qppx-4xf9-6rv9, MINI-qx7v-gg9j-942w, MINI-rc25-3mgh-gpfw, MINI-rjp7-m2wr-v2c5, MINI-rjv3-m4g2-xm82, MINI-rv28-7338-wvpg, MINI-vrpw-jj9m-34fv, MINI-w994-4w2v-p64f, MINI-wc5v-hh3q-vcrm, MINI-wchm-28w9-x3rq, MINI-wf99-8fx9-3qgh, MINI-wff5-jg5c-66jg, MINI-wg9q-m32c-66p5, MINI-whm4-8rh5-88p2, MINI-wj3h-726p-w24q, MINI-wm45-h36q-pqrj, MINI-wpqv-82xp-97fv, MINI-wvf9-w23q-5pvc, MINI-xj7g-5qj2-w67r, MINI-xmgx-jqg5-qchj, MINI-xq94-qp7m-f6ff, ROOT-APP-MAVEN-CVE-2026-45674, UBUNTU-CVE-2026-45674 ## What is CVE-2026-45674? CVE-2026-45674 is a high-severity vulnerability in Netty Netty, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-346 (Origin Validation Error), CWE-345 (Insufficient Verification of Data Authenticity) ## Which versions are affected by CVE-2026-45674? 4 open source packages ship an affected version, including io.netty:netty-resolver-dns. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.netty:netty-resolver-dns` | Maven | All versions | 4.1.135.Final | | `io.netty:netty-resolver-dns` | Maven | All versions | 4.1.135.Final | | `io.netty:netty-resolver-dns` | Maven | From 4.2.0.Final | 4.2.15.Final | | `io.netty:netty-resolver-dns` | Maven | From 4.2.0.Final | 4.2.15.Final | Products: Netty Netty. ## How do I fix CVE-2026-45674? Upgrade io.netty:netty-resolver-dns to a fixed version for your release line: 4.1.135.Final or 4.2.15.Final. ## Is CVE-2026-45674 being exploited? There is no known exploitation of CVE-2026-45674 in the wild and no public exploit code. Public exploit code: - CVE-2026-45674 / CVE-2026-47691 / CVE-2026-45673: offline checker for DNS cache poisoning in io.netty:netty-resolver-dns - and whether your app actually uses that resolver. Spring WebClient on Reactor Netty uses it by default, although it is not in your pom.xml. (github_poc): https://github.com/xiaoqiMikko/netty-resolver-dns-check ## Other vulnerabilities in Netty Netty - [CVE-2026-75595](https://insights.sbomify.com/CVE-2026-75595/): Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext (critical 9.1) - [CVE-2026-75596](https://insights.sbomify.com/CVE-2026-75596/): Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing (high 8.7) - [CVE-2026-59901](https://insights.sbomify.com/CVE-2026-59901/): Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang (high 8.7) - [CVE-2026-55851](https://insights.sbomify.com/CVE-2026-55851/): Netty codec-haproxy: Signed-Byte Sentinel Collision in HAProxyMessageDecoder Leads to Unbounded Memory Exhaustion (high 8.7) - [CVE-2026-56745](https://insights.sbomify.com/CVE-2026-56745/): Netty SpdyHttpDecoder: ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-45674 and fix it if it is affected. What it is: CVE-2026-45674 is a high-severity vulnerability in Netty Netty, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-45674 in the wild and no public exploit code. Affected packages and fixed versions: - io.netty:netty-resolver-dns (Maven): affected all versions; fixed in 4.1.135.Final - io.netty:netty-resolver-dns (Maven): affected all versions; fixed in 4.1.135.Final - io.netty:netty-resolver-dns (Maven): affected from 4.2.0.Final; fixed in 4.2.15.Final - io.netty:netty-resolver-dns (Maven): affected from 4.2.0.Final; fixed in 4.2.15.Final Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-45674/ (Markdown: https://insights.sbomify.com/CVE-2026-45674/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45674 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45674 - OSV: https://osv.dev/vulnerability/CVE-2026-45674 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-45674/ Summaries are generated and may contain mistakes; the official description above is the record.