CVE-2026-76163: 
Linux Debian 취약성 분석 및 완화

CVE-2026-76163 is a Denial of Service vulnerability in ISC BIND 9 caused by a reachable assertion failure triggered by a malicious TKEY query. When BIND is loaded with a named.conf file that contains no global options block, an unauthenticated remote attacker can send a QTYPE TKEY query that causes an assertion failure and unexpected program termination. Affected versions include BIND 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and 9.20.9-S1 through 9.20.27-S1. The vulnerability was disclosed on September 16, 2026, and carries a CVSS v3.1 base score of 7.5 (High) (Red Hat Advisory, GitHub Advisory).

The root cause is classified as CWE-617 (Reachable Assertion): BIND contains an assertion statement that can be triggered by an attacker under a specific configuration condition — the absence of a global options block in named.conf. When this configuration is present, processing a DNS query of QTYPE TKEY reaches a code path where an internal assertion fails, causing the named process to exit unexpectedly. The attack requires no authentication, no user interaction, and is exploitable over the network with low complexity, making it straightforward to trigger remotely against misconfigured servers (ISC KB, Red Hat Bugzilla).

Successful exploitation results in a complete loss of availability for the BIND DNS service, as the named process terminates unexpectedly upon receiving the malicious TKEY query. There is no impact on confidentiality or data integrity. Organizations relying on the affected BIND instance for DNS resolution would experience a service outage until the process is restarted, and repeated attacks could sustain a persistent denial of service condition (Red Hat Advisory, GitHub Advisory).

As of the disclosure date (September 16, 2026), there is no public proof-of-concept exploit and no evidence of active in-the-wild exploitation. The EPSS score is 0.0, reflecting a currently low probability of exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is limited to BIND instances specifically configured without a global options block in named.conf, which reduces the overall attack surface (GitHub Advisory, Red Hat Advisory).

1. Reconnaissance: Identify internet-facing BIND 9 DNS servers running versions 9.20.0–9.20.27, 9.21.0–9.21.25, or 9.20.9-S1–9.20.27-S1 using tools such as Shodan, Censys, or DNS banner grabbing.
2. Identify misconfiguration: Determine whether the target BIND instance is running without a global options block in its named.conf. This may be inferred from default or minimal BIND deployments.
3. Craft TKEY query: Construct a DNS query with QTYPE TKEY (query type 249) directed at the target BIND server. Standard DNS query tools such as dig or custom DNS libraries can be used: e.g., dig @<target-ip> <name> TKEY.
4. Trigger assertion failure: Send the crafted TKEY query to the target server. If the server is misconfigured (no global options block), the assertion failure is triggered and the named process exits unexpectedly, causing a DNS service outage.
5. Sustain DoS: Repeat the query after any automatic process restart to maintain the denial of service condition (ISC KB, Red Hat Bugzilla).

• Logs: Sudden termination entries in BIND/named logs (e.g., named process exit with assertion failure messages referencing TKEY query processing); entries in /var/log/syslog or /var/log/messages showing unexpected named crashes.
• Process: Unexpected termination and restart of the named process; monitoring tools (e.g., systemd, supervisord) logging repeated restarts of the BIND service.
• Network: Unusual inbound DNS queries with QTYPE TKEY (query type 249) from external or unexpected source IP addresses, particularly in high volume or repeated patterns targeting the DNS server.

ISC has released patched versions BIND 9.20.29 and 9.21.26, which address this vulnerability; administrators should upgrade immediately (ISC Downloads 9.20.29, ISC Downloads 9.21.26). As a temporary workaround, ensure that the named.conf file includes a global options block (even if empty or minimal), as this configuration change prevents the vulnerable code path from being reached. Additionally, network-level access controls (e.g., firewall rules or BIND's allow-query ACLs) can be used to restrict TKEY queries to trusted sources if immediate patching is not feasible (ISC KB, Red Hat Advisory).

The vulnerability was reported across multiple security tracking platforms including Vulners, VulDB, and oss-sec shortly after disclosure on September 16, 2026. Red Hat triaged the issue at high severity and opened a tracking bug for affected products. Coverage noted that ISC patched 14 BIND 9 vulnerabilities simultaneously in the 9.20.29 and 9.21.26 releases (Linux Compatible, oss-sec). No notable individual researcher commentary or significant social media discussion has been identified beyond standard aggregator coverage.