# Netty has a DNS Codec Input Validation Bypass (Encoder + Decoder) Advisory record · `GHSA-cm33-6792-r9fm` - **Identifiers:** `GHSA-cm33-6792-r9fm` · `CVE-2026-42579` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-626](https://cwe.mitre.org/data/definitions/626.html) · [CWE-1286](https://cwe.mitre.org/data/definitions/1286.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-626](https://agentprime.io/advisories/tag/cwe-626.md) · [CWE-1286](https://agentprime.io/advisories/tag/cwe-1286.md) - **Published:** 7 May 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 May 2026, 00:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `io.netty:netty-codec-dns` (Maven): affected `>=4.2.0.Alpha1, <4.2.13.Final || <4.1.133.Final`; fixed in `4.2.13.Final`, `4.1.133.Final` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Netty's io.netty:netty-codec-dns module, versions 4.2.0.Alpha1 up to 4.2.13.Final and 4.1.x before 4.1.133.Final, does not enforce RFC 1035 domain name limits when encoding or decoding DNS names. A malicious DNS server can send oversized labels that cause excessive memory allocation, and applications that build queries from user-supplied hostnames can produce ambiguous names, including ones with null bytes. Upgrade to 4.2.13.Final or 4.1.133.Final. The source gives few details on the exact exploit conditions. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.010, the 63rd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-cm33-6792-r9fm) ## Sources - [GitHub Advisory Database: GHSA-cm33-6792-r9fm](https://github.com/advisories/GHSA-cm33-6792-r9fm) - [OSV: GHSA-cm33-6792-r9fm](https://osv.dev/vulnerability/GHSA-cm33-6792-r9fm) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .