# CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver > An attacker can cause a denial of service in the BIND recursive resolver by triggering a use-after-free bug via crafted DNSSEC responses. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Sep 2026 - **Updated:** 17 Sep 2026 - **Also known as:** ALPINE-CVE-2026-19662, ALSA-2026:89745, ALSA-2026:89746, ALSA-2026:90328, AZL-103356, BELL-CVE-2026-19662, DEBIAN-CVE-2026-19662, ECHO-b2e2-f23e-0cd5, GHSA-pqfm-7x4v-9w63, MINI-5jxx-62pw-8p89, MINI-xmq9-jm7m-jfpc, RLSA-2026:89745, RLSA-2026:89746, RLSA-2026:90328, UBUNTU-CVE-2026-19662 ## What is CVE-2026-19662? CVE-2026-19662 is a medium-severity use after free vulnerability in ISC BIND 9, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2026-19662? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `bind` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-chroot` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-devel` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-dnssec-utils` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-doc` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-libs` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-license` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind-utils` | AlmaLinux:10 | All versions | 32:9.18.33-15.el10_2.13 | | `bind` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-chroot` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-devel` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-dnssec-doc` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-dnssec-utils` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-doc` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-libs` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-license` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind-utils` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind9.18` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `bind9.18-chroot` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `bind9.18-devel` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `bind9.18-dnssec-utils` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `bind9.18-doc` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `bind9.18-libs` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `bind9.18-utils` | AlmaLinux:9 | All versions | 32:9.18.29-14.el9_8.11 | | `python3-bind` | AlmaLinux:9 | All versions | 32:9.16.23-40.el9_8.12 | | `bind` | Rocky Linux:10 | All versions | 2:9.18.33-15.el10_2.13 | | `bind` | Rocky Linux:9 | All versions | 2:9.16.23-40.el9_8.12 | | `bind9.18` | Rocky Linux:9 | All versions | 2:9.18.29-14.el9_8.11 | ## How do I fix CVE-2026-19662? Apply the vendor's patch. ## Is CVE-2026-19662 being exploited? There is no known exploitation of CVE-2026-19662 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-19662 and fix it if it is affected. What it is: CVE-2026-19662 is a medium-severity use after free vulnerability in ISC BIND 9, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-19662 in the wild and no public exploit code. Affected product: ISC BIND 9. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-19662/ (Markdown: https://insights.sbomify.com/CVE-2026-19662/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19662 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19662 - OSV: https://osv.dev/vulnerability/CVE-2026-19662 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-19662/ Summaries are generated and may contain mistakes; the official description above is the record.