bind security update
BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly. Security Fix(es): 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.(CVE-2026-19033) An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue af
- Products
- bind
- Affected versions
- Not specified
- Fixed versions
- 9.18.21-14.oe2403sp3
- CVEs
- CVE-2026-19033, CVE-2026-19662, CVE-2026-19941, CVE-2026-75029, CVE-2026-78301
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 20:40 UTC · Revision 1
Source evidence
BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly. Security Fix(es): 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.(CVE-2026-19033) An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue af
osv:OESA-2026-4340
bind
Fixed versions: 9.18.21-14.oe2403sp3
Complete source record
{
"id": "f6257f0a25a7cb5b92fe7df79f4f6e9daa6784f953cf49970ce4f22f793741ca",
"url": "https://osv.dev/vulnerability/OESA-2026-4340",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "bind security update",
"summary": "BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols. BIND includes a DNS server (named), which resolves host names to IP addresses; a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating properly. Security Fix(es): 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.(CVE-2026-19033) An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a particular sequence of crafted answers, and those answers arrive in a particular order with particular timing, the `named` resolver will encounter a use-after-free bug, and abort. This issue af",
"evidence": "osv:OESA-2026-4340",
"products": [
{
"name": {
"value": "bind",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "9.18.21-14.oe2403sp3",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "OESA-2026-4340",
"aliases": [
"OESA-2026-4340"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "9.18.21-14.oe2403sp3"
}
]
}
],
"package": {
"name": "bind",
"purl": "pkg:rpm/openEuler/bind&distro=openEuler-24.03-LTS-SP3",
"ecosystem": "openEuler:24.03-LTS-SP3"
},
"database_specific": {
"source": "https://repo.openeuler.org/security/data/osv/OESA-2026-4340.json"
},
"ecosystem_specific": {
"src": [
"bind-9.18.21-14.oe2403sp3.src.rpm"
],
"noarch": [
"bind-dnssec-doc-9.18.21-14.oe2403sp3.noarch.rpm",
"bind-license-9.18.21-14.oe2403sp3.noarch.rpm"
],
"x86_64": [
"bind-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-chroot-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-debuginfo-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-debugsource-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-devel-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-dnssec-utils-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-libs-9.18.21-14.oe2403sp3.x86_64.rpm",
"bind-utils-9.18.21-14.oe2403sp3.x86_64.rpm"
],
"aarch64": [
"bind-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-chroot-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-debuginfo-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-debugsource-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-devel-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-dnssec-utils-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-libs-9.18.21-14.oe2403sp3.aarch64.rpm",
"bind-utils-9.18.21-14.oe2403sp3.aarch64.rpm"
]
}
}
],
"modified": "2026-10-16T12:15:13.595216371Z",
"provider": "osv",
"upstream": [
"CVE-2026-19033",
"CVE-2026-19662",
"CVE-2026-19941",
"CVE-2026-75029",
"CVE-2026-78301"
],
"references": [
"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4340",
"https://nvd.nist.gov/vuln/detail/CVE-2026-19033",
"https://nvd.nist.gov/vuln/detail/CVE-2026-19662",
"https://nvd.nist.gov/vuln/detail/CVE-2026-19941",
"https://nvd.nist.gov/vuln/detail/CVE-2026-75029",
"https://nvd.nist.gov/vuln/detail/CVE-2026-78301"
],
"provider_metadata": {
"severity": "Medium"
}
},
"related_cves": [
{
"value": "CVE-2026-19033",
"evidence": "/upstream"
},
{
"value": "CVE-2026-19662",
"evidence": "/upstream"
},
{
"value": "CVE-2026-19941",
"evidence": "/upstream"
},
{
"value": "CVE-2026-75029",
"evidence": "/upstream"
},
{
"value": "CVE-2026-78301",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 340838,
"published_at": "2026-10-16T11:59:32+00:00"
}