ISC BIND 9
Concurrent GSS-TSIG messages corrupt memory
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`". An attacker who can capture a previously signed 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. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 9.11.0, <= 9.18.50
- >= 9.20.0, <= 9.20.29
- >= 9.21.0, <= 9.21.26
- >= 9.11.3-S1, <= 9.18.50-S1
- >= 9.20.9-S1, <= 9.20.29-S1
Mitigation
Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.30, 9.21.27, or 9.20.30-S1.
Workaround
No workarounds known.
References
- Vendor advisory kb.isc.org/docs/cve-2026-94300
- Patch downloads.isc.org/isc/bind9/9.20.30
- Patch downloads.isc.org/isc/bind9/9.21.27
Timeline
Days relative to CVE publicationFirst public PoC 1.8 days after publication; not in CISA KEV. First PoC: Ibonok/CVE-2026-94300 (created 23 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| Ibonok/CVE-2026-94300 | 23 Oct 2026 +1.8 d | 14 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.