# CVE-2026-35406: Aardvark-dns has incorrect error handling for malformed tcp packets > A malformed TCP packet sequence causes the Aardvark-dns container service to enter an infinite loop, consuming all CPU resources and denying service. - **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Apr 2026 - **Updated:** 8 Apr 2026 - **Also known as:** ALSA-2026:36318, ALSA-2026:36782, BELL-CVE-2026-35406, DEBIAN-CVE-2026-35406, GHSA-hfpq-x728-986j, RHSA-2026:36318, RHSA-2026:36782, RLSA-2026:36318, RLSA-2026:36782, UBUNTU-CVE-2026-35406, openSUSE-SU-2026:10570-1 ## What is CVE-2026-35406? CVE-2026-35406 is a medium-severity denial of service vulnerability in containers aardvark-dns, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Aardvark-dns is an authoritative dns server for A/AAAA container records. From 1.16.0 to 1.17.0, a truncated TCP DNS query followed by a connection reset causes aardvark-dns to enter an unrecoverable infinite error loop at 100% CPU. This vulnerability is fixed in 1.17.1. Weakness: CWE-835 (Loop with Unreachable Exit Condition), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-35406? 2 open source packages ship an affected version, including netavark. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `netavark` | crates.io | From 1.16.0 | 1.17.1 | | `netavark` | crates.io | From 1.16.0 | 1.17.1 | | `aardvark-dns` | AlmaLinux:10 | All versions | 2:1.17.1-1.el10_2 | | `aardvark-dns` | AlmaLinux:9 | All versions | 2:1.17.1-1.el9_8 | | `aardvark-dns` | Red Hat:enterprise_linux:10.2 | All versions | 2:1.17.1-1.el10_2 | | `aardvark-dns-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 2:1.17.1-1.el10_2 | | `aardvark-dns-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 2:1.17.1-1.el10_2 | | `aardvark-dns` | Red Hat:enterprise_linux:9::appstream | All versions | 2:1.17.1-1.el9_8 | | `aardvark-dns-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 2:1.17.1-1.el9_8 | | `aardvark-dns-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 2:1.17.1-1.el9_8 | | `aardvark-dns` | Rocky Linux:10 | All versions | 2:1.17.1-1.el10_2 | | `aardvark-dns` | Rocky Linux:9 | All versions | 2:1.17.1-1.el9_8 | | `aardvark-dns` | openSUSE:Tumbleweed | All versions | 1.17.1-1.1 | Products: Containers Aardvark-Dns. ## How do I fix CVE-2026-35406? Upgrade netavark to 1.17.1 or later. ## Is CVE-2026-35406 being exploited? There is no known exploitation of CVE-2026-35406 in the wild and no public exploit code. ## Other vulnerabilities in containers aardvark-dns - [CVE-2024-8418](https://insights.sbomify.com/CVE-2024-8418/): Containers/aardvark-dns: tcp query handling flaw in aardvark-dns leading to denial of service (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-35406 and fix it if it is affected. What it is: CVE-2026-35406 is a medium-severity denial of service vulnerability in containers aardvark-dns, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-35406 in the wild and no public exploit code. Affected packages and fixed versions: - netavark (crates.io): affected from 1.16.0; fixed in 1.17.1 - netavark (crates.io): affected from 1.16.0; fixed in 1.17.1 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-35406/ (Markdown: https://insights.sbomify.com/CVE-2026-35406/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35406 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35406 - OSV: https://osv.dev/vulnerability/CVE-2026-35406 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-35406/ Summaries are generated and may contain mistakes; the official description above is the record.