Quick answers
- Is CVE-2026-94300 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94300 being exploited in the wild.
- How severe is CVE-2026-94300?
- High severity, with a CVSS score of 8.1, published 21 October 2026.
- Which products and versions are affected?
- Isc Bind 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, 9.20.9-S1 through 9.20.29-S1.
- Is there a fix for CVE-2026-94300?
- Yes: fixed in BIND 9.18.51, 9.20.30, 9.21.27, 9.18.51-S1, 9.20.30-S1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94300 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-94300?
- Check whether you run Isc Bind at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: BIND 9.18.51, 9.20.30, 9.21.27, 9.18.51-S1, 9.20.30-S1
Technical details
GSS-TSIG replay vulnerability in BIND's named daemon: an attacker can capture and replay previously signed UDP TSIG messages before the negotiated key expires. By combining replay with crafted queries to a zone under attacker control, remote code execution may be achieved through heap corruption. This affects BIND 9.11.0–9.21.26 and several supported security release branches.
Affected products
- ISC BIND 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, 9.20.9-S1 through 9.20.29-S1
Timeline
- 2026-10-21: disclosed