cve.bz

CVE-2026-78301 isc bind 9

5.8 mediumEPSS 0.2%

Medium (5.8) in isc bind 9. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose authoritative status and return an out-of-zone delegation. On a server that also provides recursion BIND can follow this locally sourced cut and cache attacker-supplied data, affecting names outside the configured zone. This situation persists as long as the malformed zone remains in the zone database. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

Severity

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-17. 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-349 Acceptance of Extraneous Untrusted Data With Trusted Data
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-78301 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78301?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78301?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-78301 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.

Affected

  • isc:bind 9

Versions

From the CNA's record in the CVE List.

ProductAffected
ISC BIND 9from 9.11.0 through 9.18.50
ISC BIND 9from 9.20.0 through 9.20.27
ISC BIND 9from 9.21.0 through 9.21.25
ISC BIND 9from 9.11.3-S1 through 9.18.50-S1
ISC BIND 9from 9.20.9-S1 through 9.20.27-S1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12bind91:9.18.49-1~deb12u3DEBIAN-CVE-2026-78301
Debian13bind91:9.20.29-1~deb13u1DEBIAN-CVE-2026-78301
Debian14bind91:9.20.29-1DEBIAN-CVE-2026-78301
Ubuntu18.04:LTS, 24.04:LTS, 26.04:LTSisc-dhcpno fix listedUBUNTU-CVE-2026-78301
Ubuntu20.04:LTS, 22.04:LTSbind9-libsno fix listedUBUNTU-CVE-2026-78301
Ubuntu22.04:LTSbind91:9.18.39-0ubuntu0.22.04.7UBUNTU-CVE-2026-78301 USN-8929-1 USN-8969-1
Ubuntu24.04:LTSbind91:9.18.39-0ubuntu0.24.04.8UBUNTU-CVE-2026-78301 USN-8929-1 USN-8969-1
Ubuntu26.04:LTSbind91:9.20.24-1ubuntu0.4UBUNTU-CVE-2026-78301 USN-8929-1 USN-8969-1
Ubuntu26.10bind91:9.20.24-1ubuntu3.1UBUNTU-CVE-2026-78301 USN-8969-1
UbuntuPro:14.04:LTSbind91:9.9.5.dfsg-3ubuntu0.19+esm15UBUNTU-CVE-2026-78301 USN-8929-1
UbuntuPro:16.04:LTSbind91:9.10.3.dfsg.P4-8ubuntu1.19+esm11UBUNTU-CVE-2026-78301 USN-8929-1
UbuntuPro:18.04:LTSbind91:9.11.3+dfsg-1ubuntu1.19+esm6UBUNTU-CVE-2026-78301 USN-8929-1
UbuntuPro:20.04:LTSbind91:9.18.30-0ubuntu0.20.04.2+esm3UBUNTU-CVE-2026-78301 USN-8929-1
Red Hathummingbird:1bind, bind-doc, bind-libs and 4 more32:9.20.29-0.1.hum1RHSA-2026:68279
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Server 15 SP4-LTSS and 1 morebind9.16.50-150400.5.70.1SUSE-SU-2026:4664-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morebind9.16.50-150500.8.46.1SUSE-SU-2026:4772-1
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Server Applications 15 SP7bind9.20.29-150700.3.32.2SUSE-SU-2026:4285-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5bind9.11.22-3.77.1SUSE-SU-2026:4635-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6bind9.18.50-150600.3.35.1SUSE-SU-2026:4608-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0bind9.20.29-160000.1.1SUSE-SU-2026:24157-1
SUSEMulti Linux Manager Tools SLE-Micro-5bind9.16.6-150000.12.97.1SUSE-SU-2026:5118-1
openSUSELeap 16.0bind9.20.29-160000.1.1openSUSE-SU-2026:22049-1
openSUSETumbleweedbind9.20.29-1.1openSUSE-SU-2026:11916-1
Alpinev3.22, v3.23, v3.24bind9.20.29-r0ALPINE-CVE-2026-78301
Azure Linux3bind9.20.30-1AZL-103332
Alpaquita23, 25, streambind9.20.29-r0BELL-CVE-2026-78301

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 Moderate.

Red Hat's statement

Moderate impact. BIND servers configured for both authoritative and recursive functions are vulnerable to DNS cache poisoning. An attacker who can insert a malformed zone, for example via zone transfer, can cause the server to cache attacker-supplied data for names outside the configured zone.

Red Hat's mitigation

To mitigate this issue, Red Hat recommends separating authoritative and recursive DNS functions onto different BIND instances or servers. This prevents a compromised authoritative zone from affecting recursive queries. Additionally, restrict zone transfer sources to trusted hosts only by configuring `allow-transfer` directives within your `named.conf` zone definitions. After modifying `named.conf`, the BIND service must be reloaded for changes to take effect, which may temporarily interrupt DNS resolution.

ProductPackageStateAdvisory
Red Hat Hardened Imagesbind-main-9.20.29-0.1.hum1Fixed 2026-09-16RHSA-2026:68279
Red Hat Enterprise Linux 10bindFix deferred
Red Hat Enterprise Linux 6bindNot affected
Red Hat Enterprise Linux 7bindFix deferred
Red Hat Enterprise Linux 8bindFix deferred
Red Hat Enterprise Linux 8bind9.16Fix deferred
Red Hat Enterprise Linux 9bindFix deferred
Red Hat Enterprise Linux 9bind9.18Fix deferred
Red Hat Enterprise Linux 9dhcpNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

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-78301.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-141 Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON