Article
BIND 9 CVE-2026-94300: Fixed Versions and How to Check Your Exposure
ISC fixed a BIND 9 vulnerability in GSS-TSIG that can corrupt memory and may allow code execution. Fixed versions, who is exposed and a…
Quick links
Press Enter to search, Esc to close
Vulnerability
A memory corruption flaw in the GSS-TSIG handling of the BIND 9 name server.
In short
CVE-2026-94300 is a memory corruption flaw in the GSS-TSIG handling of the BIND 9 name server. ISC says replaying a signed GSS-TSIG UDP message while its key is valid, together with crafted queries to a zone the attacker controls, may lead to remote code execution. ISC rates it High with a CVSS score of 8.1 and fixed it in 9.20.30, 9.21.27 and 9.20.30-S1 on 21 October 2026.
ISC says an attacker who has captured a previously signed GSS-TSIG UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote code execution in the named process. The impact ISC lists is memory corruption, leading to program abort and/or potential remote code execution.
The CVSS vector is network, high attack complexity, no privileges and no user interaction. Red Hat rates it Important rather than Critical because exploitation depends on capturing active keys within their validity window.
Red Hat adds that BIND on Red Hat Enterprise Linux does not enable GSS-TSIG by default. The risk is mainly for servers tied to Kerberos identity systems such as FreeIPA or Active Directory. Read our BIND 9 fixed versions and exposure check for the patched releases and how to check a server.
BIND 9.11.0 to 9.18.50, 9.20.0 to 9.20.29 and 9.21.0 to 9.21.26. Supported Preview Edition 9.11.3-S1 to 9.18.50-S1 and 9.20.9-S1 to 9.20.29-S1. Fixed in 9.20.30, 9.21.27 and 9.20.30-S1.
ISC lists no fixed 9.18 release, and its download page shows 9.18 as end of life, with 9.18.50 as the last release. Distribution builds use their own numbers: the Debian tracker shows trixie fixed in 1:9.20.30-1~deb13u1 and bookworm (9.18) as vulnerable.
ISC fixes CVE-2026-3039, a memory exhaustion flaw in GSS-API TKEY negotiation, in 9.18.49, 9.20.23 and 9.21.22.
ISC's revision history lists an early notification for CVE-2026-94300.
ISC publishes the advisory and releases 9.20.30, 9.21.27 and 9.20.30-S1. The CVE record is published the same day.
The CISA coordinator entry marks exploitation as none, automatable as no and technical impact as total. The CISA KEV release of 14:04 UTC does not list the CVE.
JPRS and CERT.LV post alerts on X.
Run named -v for the installed version and rndc version for the running one. Anything in the affected ranges needs the upgrade.
Run named-checkconf -p -x and search for tkey-gssapi-keytab and tkey-gssapi-credential, the directives Red Hat names. Servers with either one go first.
Move to 9.20.30, 9.21.27 or 9.20.30-S1, or to your distribution's fixed build, then restart named and confirm the running version.
ISC lists no workarounds. Red Hat suggests removing the GSS-TSIG directives or limiting port 53 to trusted networks. That can break Kerberos-authenticated dynamic DNS in Active Directory or IdM setups.
It is a memory corruption flaw in how BIND 9 handles GSS-TSIG messages. ISC says it may allow remote code execution and rates it High, CVSS 8.1.
BIND 9.20.30, 9.21.27 and the Supported Preview Edition 9.20.30-S1. ISC lists no fixed 9.18 release.
ISC does not name the needed configuration. Red Hat says the risk is for servers that negotiate GSS-TSIG keys, such as those tied to FreeIPA or Active Directory. Check for tkey-gssapi-keytab.
ISC says it knows of no active exploits, and the CISA catalog did not list it in its 21 October release.
Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.