CVE-2026-3039: BIND TKEY Authentication Memory Consumption Vulnerability
BIND servers configured for TKEY-based authentication using GSS-API tokens are susceptible to excessive memory consumption upon receiving and processing crafted packets, impacting availability.
ISC BIND 9 is vulnerable to excessive memory consumption (CVE-2026-3039) when processing maliciously crafted packets targeting servers using TKEY-based authentication via GSS-API tokens. This configuration is often found in Active Directory-integrated DNS deployments or Kerberos-secured DNS environments. An attacker can exploit this vulnerability by sending specially crafted packets, causing the BIND server to consume excessive memory resources, potentially leading to denial of service. The affected versions include BIND 9 versions 9.0.0 through 9.16.50, 9.18.0 through 9.18.48, 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, 9.9.3-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.48-S1, and 9.20.9-S1 through 9.20.22-S1. Defenders should monitor DNS server memory usage and implement rate limiting or packet filtering to mitigate the risk.
Attack Chain
- The attacker identifies a BIND server configured to use TKEY-based authentication with GSS-API.
- The attacker crafts a malicious DNS packet specifically designed to exploit the memory consumption vulnerability.
- The attacker sends the crafted packet to the vulnerable BIND server.
- The BIND server receives the packet and attempts to process the TKEY authentication.
- Due to the malicious structure of the packet, the server allocates an excessive amount of memory during the authentication process.
- The attacker repeats steps 3-5, sending multiple crafted packets to continually exhaust server memory.
- The BIND server’s memory consumption increases significantly, impacting performance and stability.
- The BIND server eventually crashes due to memory exhaustion, resulting in a denial-of-service condition.
Impact
Successful exploitation of CVE-2026-3039 leads to excessive memory consumption on the affected BIND server, potentially resulting in a denial-of-service condition. This can disrupt DNS resolution services for the affected domain or network, impacting users’ ability to access websites and online services. The vulnerability poses a significant risk to organizations relying on Active Directory-integrated DNS or Kerberos-secured DNS environments, potentially causing widespread service outages.
Recommendation
- Upgrade BIND 9 to a patched version beyond 9.16.50, 9.18.48, 9.20.22, or 9.21.21 to remediate CVE-2026-3039.
- Implement rate limiting on DNS traffic to mitigate the impact of malicious packets, protecting against memory exhaustion.
- Monitor DNS server memory usage for unexpected spikes using system monitoring tools.
- Deploy the Sigma rule
Detect Excessive DNS Server Memory Allocationto identify potential exploitation attempts. - Review DNS server configurations to minimize the use of TKEY-based authentication where possible.
Detection coverage 2
Detect Excessive DNS Server Memory Allocation
mediumDetects high memory usage by named/BIND process, potentially indicating CVE-2026-3039 exploitation.
Detect Windows DNS Service High Memory Usage
mediumDetects high memory usage by the Windows DNS service, potentially indicating CVE-2026-3039 exploitation.
Detection queries are available on the platform. Get full rules →