Skip to content
fr Sign in
6.5 Medium

CVE-2026-19033 For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone…

Description

For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. 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.

Affected products and versions

Product Affected versions Fixed in
BIND 9 9.21 9.21.0 → 9.21.25 No fix stated
BIND 9 9.20 9.20.0 → 9.20.27 No fix stated
BIND 9 9.11 9.11.0 → 9.18.50 No fix stated

References

Timeline

  1. Published
  2. Last modified

Other CVEs of BIND 9

The 87 CVEs of BIND 9 →
CVE-2026-97313 A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may… 7.5 High CVE-2026-96888 A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an… 7.5 High CVE-2026-94300 Replaying GSS-TSIG signed UDP messages can result in memory corruption in "`named`" 8.1 High CVE-2026-19630 In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with… 7.5 High
Track this CVE