CVE-2026-35406: containers aardvark-dns · Uncontrolled Resource Consumption
Affects containers aardvark-dnsSource CVE Database V5
Not known to be exploited · CVSS 6.2 Medium : upgrade to 1.17.1 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.17.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade aardvark-dns and containers/aardvark-dns to 1.17.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| containersaardvark-dns | Affected
| Fixed in
|
GitHubcontainers/aardvark-dnspkg:github/containers/aardvark-dnsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade aardvark-dns to version 1.17.1 or later where this vulnerability is fixed. Patch status is confirmed by the version information in the description. No other mitigation steps are indicated.
Description
CVE-2026-35406 is a medium severity vulnerability in aardvark-dns versions 1.16.0 through 1.17.0. It involves uncontrolled resource consumption where a truncated TCP DNS query followed by a connection reset causes the server to enter an unrecoverable infinite error loop at 100% CPU usage. This results in a denial of service condition. The issue is fixed in version 1.17.1.