All reports
Medium

UBUNTU-CVE-2026-19033

Affected versions

Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<1:9.18.39-0ubuntu0.22.04.7
Fixed version
1:9.18.39-0ubuntu0.22.04.7
Affected versions
<1:9.18.39-0ubuntu0.24.04.8
Fixed version
1:9.18.39-0ubuntu0.24.04.8
Affected versions
*
Fixed version
Not reported
Affected versions
<1:9.20.24-1ubuntu0.4
Fixed version
1:9.20.24-1ubuntu0.4
Affected versions
*
Fixed version
Not reported
Affected versions
<1:9.20.24-1ubuntu3.1
Fixed version
1:9.20.24-1ubuntu3.1
Affected versions
<1:9.9.5.dfsg-3ubuntu0.19+esm15
Fixed version
1:9.9.5.dfsg-3ubuntu0.19+esm15
Affected versions
<1:9.10.3.dfsg.P4-8ubuntu1.19+esm11
Fixed version
1:9.10.3.dfsg.P4-8ubuntu1.19+esm11
Affected versions
<1:9.11.3+dfsg-1ubuntu1.19+esm6
Fixed version
1:9.11.3+dfsg-1ubuntu1.19+esm6
Affected versions
<1:9.18.30-0ubuntu0.20.04.2+esm3
Fixed version
1:9.18.30-0ubuntu0.20.04.2+esm3

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.

Links