OESA-2026-4666 (CVE-2026-19630)
Vulnerability from osv_openeuler – Published: 2026-11-04 13:54 – Updated: 2026-11-04 13:54 – Source websiteBerkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols and provides an openly redistributable reference implementation of the major components of the Domain Name System. This package includes the components to operate a DNS server.
Security Fix(es):
In a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with no limit imposed by BIND. A DNS message with a maliciously large number of such structures will cause BIND to consume disproportionate amounts of CPU time and memory during processing. This issue affects BIND 9 versions 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, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-19630)
Replaying GSS-TSIG signed UDP messages can result in memory corruption in "named". An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote code execution.
This issue affects BIND 9 versions 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, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-94300)
A BIND resolver that is configured with both a "redirect" zone and "qname-minimization strict" may abort with an assertion failure while processing the redirect. This issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-96888)
A recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of "recursive-only yes", and the other with "recursive-only no". This issue affects BIND 9 versions 9.16.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, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-97313)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bind-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-chroot-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-debuginfo-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-debugsource-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-devel-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-dnssec-utils-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-libs-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-pkcs11-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-pkcs11-devel-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-pkcs11-libs-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-pkcs11-utils-9.16.23-34.oe2203sp4.aarch64.rpm",
"bind-utils-9.16.23-34.oe2203sp4.aarch64.rpm"
],
"noarch": [
"bind-dnssec-doc-9.16.23-34.oe2203sp4.noarch.rpm",
"bind-license-9.16.23-34.oe2203sp4.noarch.rpm",
"python3-bind-9.16.23-34.oe2203sp4.noarch.rpm"
],
"src": [
"bind-9.16.23-34.oe2203sp4.src.rpm"
],
"x86_64": [
"bind-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-chroot-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-debuginfo-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-debugsource-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-devel-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-dnssec-utils-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-libs-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-pkcs11-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-pkcs11-devel-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-pkcs11-libs-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-pkcs11-utils-9.16.23-34.oe2203sp4.x86_64.rpm",
"bind-utils-9.16.23-34.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "bind",
"purl": "pkg:rpm/openEuler/bind\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "9.16.23-34.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols and provides an openly redistributable reference implementation of the major components of the Domain Name System. This package includes the components to operate a DNS server.\r\n\r\nSecurity Fix(es):\n\nIn a BIND resolver, inbound DNS protocol messages with a particular structure will result in additional processing, with no limit imposed by BIND. A DNS message with a maliciously large number of such structures will cause BIND to consume disproportionate amounts of CPU time and memory during processing.\nThis issue affects BIND 9 versions 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, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-19630)\n\nReplaying GSS-TSIG signed UDP messages can result in memory corruption in \u0026quot;`named`\u0026quot;. An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid. By also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote code execution.\nThis issue affects BIND 9 versions 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, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-94300)\n\nA BIND resolver that is configured with both a \u0026quot;redirect\u0026quot; zone and \u0026quot;qname-minimization strict\u0026quot; may abort with an assertion failure while processing the redirect.\nThis issue affects BIND 9 versions 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.16.8-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-96888)\n\nA recursive BIND server that receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0) may exit with an assertion failure, resulting in a denial of service. To be vulnerable, the BIND server must allow recursive queries and have at least two RPZ zones configured: one with the default setting of \u0026quot;recursive-only yes\u0026quot;, and the other with \u0026quot;recursive-only no\u0026quot;.\nThis issue affects BIND 9 versions 9.16.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, and 9.20.9-S1 through 9.20.29-S1.(CVE-2026-97313)",
"id": "OESA-2026-4666",
"modified": "2026-11-04T13:54:16Z",
"published": "2026-11-04T13:54:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4666"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-19630"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-94300"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-96888"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97313"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "bind security update",
"upstream": [
"CVE-2026-19630",
"CVE-2026-94300",
"CVE-2026-96888",
"CVE-2026-97313"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.