CVE-2026-19033

The record

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 packages

Related vulnerabilities

• CVE-2026-78301 A malformed zone may contain an NS or DNAME node above its origin, which `named` treats… CWE-349
• CVE-2026-50252 In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized… CWE-349
• CVE-2026-41120 Dell Wyse Management Suite, versions prior to WMS 5.5 HF1, contain an Acceptance of… CWE-349
• CVE-2026-33612 A malicious authoritative server can send a crafted zone via the ZoneToCache function… CWE-349
• CVE-2026-46342 Nuxt is an open-source web development framework for Vue.js. CWE-349
• CVE-2026-45602 No cwe for this issue in Windows DHCP Server allows an unauthorized attacker to perform… CWE-349
• CVE-2026-42960 NLnet Labs Unbound up to and including version 1.25.0 is vulnerable to poisoning via… CWE-349
• GHSA-g8wj-3cr3-6w7v Nuxt: `__nuxt_island` endpoint does not bind responses to request props, enabling… CWE-349