Quick answers
- Is CVE-2026-35406 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35406 being exploited in the wild.
- How severe is CVE-2026-35406?
- High severity, with a CVSS score of 7.5, published 7 April 2026.
- Which products and versions are affected?
- Containers Aardvark-Dns >= 1.16.0, < 1.17.1; netavark (crates.io) >= 1.16.0, <= 1.17.0, SEMVER:introduced=1.16.0,fixed=1.17.1.
- Is there a fix for CVE-2026-35406?
- Yes. netavark (crates.io): upgrade to 1.17.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35406 attacked?
- It is attacked over the network or with local access, in a hosted service.
- Am I affected by CVE-2026-35406?
- Check whether you run Containers Aardvark-Dns or netavark (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- netavark (crates.io): upgrade to 1.17.1 or later
cargo update -p netavark
Technical details
Aardvark-dns (versions 1.16.0 to 1.17.0) fails to correctly handle errors during TCP stream processing. Specifically, a truncated TCP DNS query followed immediately by a connection reset (RST) triggers an unrecoverable infinite error loop (CWE-835). This occurs because the server fails to abort the TCP stream upon encountering the malformed packet and instead retries the operation indefinitely, consuming 100% of the CPU. While some metrics suggest a local attack vector, the nature of DNS services often exposes this to the network. The issue is resolved in version 1.17.1 by ensuring the TCP stream is correctly terminated on error.
Affected products
- containers aardvark-dns >= 1.16.0, < 1.17.1
Identifiers
- CVE-2026-35406
- GHSA-hfpq-x728-986j
Timeline
- 2026-04-07: disclosed
- 2026-04-07: patched: Fixed in version 1.17.1
- 2026-04-07: advisory