cve.bz

CVE-2026-12617 isc bind: Reachable Assertion

7.5 highEPSS 0.5%

High (7.5) in isc bind. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative server responds positively to the A query but delays the DNAME response and later responds negatively, `named` may quit unexpectedly. Or, if a client queries for a CNAME and A record for the same name to the resolver, and the authoritative server responds positively to the A query but delays the CNAME response and later responds with a self-referential CNAME, the same failure may occur. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.18.11-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 45th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-617 Reachable Assertion
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-12617 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-12617?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-12617?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-12617 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-12617

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-12617](https://cve.bz/cve/badge/CVE-2026-12617.svg)](https://cve.bz/cve/CVE-2026-12617)

HTML:

<a href="https://cve.bz/cve/CVE-2026-12617"><img src="https://cve.bz/cve/badge/CVE-2026-12617.svg" alt="CVE-2026-12617"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ISC BIND 9from 9.18.0 through 9.18.50
ISC BIND 9from 9.20.0 through 9.20.24
ISC BIND 9from 9.18.11-S1 through 9.18.50-S1
ISC BIND 9from 9.20.9-S1 through 9.20.24-S1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12bind91:9.18.49-1~deb12u2DEBIAN-CVE-2026-12617
Debian13bind91:9.20.26-1~deb13u1DEBIAN-CVE-2026-12617
Debian14bind91:9.20.26-1DEBIAN-CVE-2026-12617
Ubuntu18.04:LTS, 24.04:LTS, 26.04:LTSisc-dhcpno fix listedUBUNTU-CVE-2026-12617
Ubuntu20.04:LTS, 22.04:LTSbind9-libsno fix listedUBUNTU-CVE-2026-12617
Ubuntu22.04:LTSbind91:9.18.39-0ubuntu0.22.04.5UBUNTU-CVE-2026-12617 USN-8648-1
Ubuntu24.04:LTSbind91:9.18.39-0ubuntu0.24.04.6UBUNTU-CVE-2026-12617 USN-8648-1
Ubuntu26.04:LTSbind91:9.20.24-1ubuntu0.2UBUNTU-CVE-2026-12617 USN-8648-1
Red Hathummingbird:1bind, bind-doc, bind-libs and 4 more32:9.20.26-0.1.hum1RHSA-2026:54071
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Server Applications 15 SP7bind9.20.26-150700.3.29.1SUSE-SU-2026:3426-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6bind9.18.50-150600.3.32.1SUSE-SU-2026:3452-1
openSUSELeap 16.0bind9.20.26-160000.1.1openSUSE-SU-2026:21489-1
openSUSETumbleweedbind9.20.26-1.1openSUSE-SU-2026:11375-1
Alpinev3.22, v3.23, v3.24bind9.20.26-r0ALPINE-CVE-2026-12617
Azure Linux3bind9.20.26-1AZL-93138
Alpaquita23, 25, streambind9.20.26-r0BELL-CVE-2026-12617

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpine · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This Important flaw in BIND can lead to a denial of service in Red Hat products. The `named` daemon may terminate unexpectedly when processing specific CNAME/DNAME and A record query orderings, coupled with precisely timed authoritative server responses. Exploitation requires an attacker to manipulate DNS responses from an authoritative server to a vulnerable resolver.

ProductPackageStateAdvisory
Red Hat Hardened Imagesbind-main-9.20.26-0.1.hum1Fixed 2026-08-12RHSA-2026:54071
Red Hat Enterprise Linux 10bindNot affected
Red Hat Enterprise Linux 6bindNot affected
Red Hat Enterprise Linux 7bindNot affected
Red Hat Enterprise Linux 8bindNot affected
Red Hat Enterprise Linux 8bind9.16Not affected
Red Hat Enterprise Linux 9bindNot affected
Red Hat Enterprise Linux 9bind9.18Not affected
Red Hat Enterprise Linux 9dhcpNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-12617.

References

Check your stackJSON