RHSA-2026:36782MediumCVSS 6.5

Red Hat Security Advisory: aardvark-dns security update

Published
July 8, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (1)

CVE-2026-35406 →

📋 Description

CVE-2026-35406 — aardvark-dns: Aardvark-dns: Denial of Service via truncated TCP DNS query and connection reset

🎯 Affected products14

  • Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-2:1.17.1-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-2:1.17.1-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-2:1.17.1-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-2:1.17.1-1.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-2:1.17.1-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debuginfo-2:1.17.1-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debuginfo-2:1.17.1-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debuginfo-2:1.17.1-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debuginfo-2:1.17.1-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debugsource-2:1.17.1-1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debugsource-2:1.17.1-1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debugsource-2:1.17.1-1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • aardvark-dns-debugsource-2:1.17.1-1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: As a mitigation, avoid using aardvark-dns when container name resolution is not required by creating Podman networks with DNS disabled (e.g., podman network create --disable-dns). This prevents the vulnerable component from being used.

🔗 References (4)