Aardvark-dns has incorrect error handling for malformed tcp packets
Summary
| CVE | CVE-2026-35406 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-07 22:16:23 UTC |
| Updated | 2026-04-08 21:27:00 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 6.2 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.000120000 probability, percentile 0.016060000 (date 2026-04-09)
Problem Types: CWE-400 | CWE-400 CWE-400: Uncontrolled Resource Consumption
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 6.2 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | CNA | DECLARED | 6.2 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Containers | Aardvark-dns | affected >= 1.16.0, < 1.17.1 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/containers/aardvark-dns/releases/tag/v1.17.1 | [email protected] | github.com | |
| github.com/containers/aardvark-dns/security/advisories/GHSA-hfpq-x728-986j | [email protected] | github.com | |
| github.com/containers/aardvark-dns/commit/3b49ea7b38bdea134b7f03256f2e13... | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.