CVE-2026-3039: BIND 9 server memory exhaustion during GSS-API TKEY negotiation
BIND servers that are configured to use TKEY-based authentication via GSS-API tokens are vulnerable to excessive memory consumption when receiving and processing maliciously-constructed packets. Typically these servers will be found in Active Directory integrated DNS deployments and/or Kerberos-secured DNS environments.
This issue affects 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.
Security readout for executives and security teams
Plain-English summary
This vulnerability can let an unauthenticated network attacker make certain BIND 9 DNS servers consume excessive memory. The main business risk is DNS disruption, especially in Active Directory integrated or Kerberos-secured DNS environments using TKEY authentication with GSS-API tokens.
Executive priority
Treat as a high-priority DNS availability issue. Patch exposed or identity-integrated DNS servers quickly because disruption to DNS can affect authentication, application access, and internal operations, even though the provided evidence does not show active exploitation.
Technical view
CVE-2026-3039 affects BIND 9 servers configured for TKEY-based authentication using GSS-API tokens. Maliciously constructed packets can cause excessive memory consumption. The CVSS 3.1 score is 7.5, with network attack vector, low complexity, no privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most likely where BIND 9 supports Kerberos-secured DNS, Active Directory integrated DNS, or TKEY/GSS-API authentication. Affected ranges include multiple ISC BIND 9 stable and subscription branches through 9.16.50, 9.18.48, 9.20.22, and 9.21.21.
Exploitation context
The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. The attack is network reachable and unauthenticated when vulnerable configuration is present, but evidence here supports denial of service through memory exhaustion only.
Researcher notes
Key scoping variable is configuration: BIND 9 must use TKEY-based authentication via GSS-API tokens. The bundle names CWE-770 and CWE-771 resource allocation issues and provides fixed ISC release references, but does not include packet details or exploit indicators.
Mitigation direction
Upgrade affected ISC BIND 9 deployments to a fixed vendor release.
Use ISC 9.18.49, 9.20.23, or 9.21.22 where applicable.
Apply relevant Red Hat errata for vendor-packaged BIND deployments.
Prioritize AD integrated and Kerberos-secured DNS environments.
Check ISC or OS vendor guidance before changing TKEY/GSS-API settings.
Validation and detection
Inventory BIND 9 versions across authoritative and recursive DNS servers.
Identify servers configured for TKEY authentication using GSS-API tokens.
Confirm packages are newer than the affected branch limits.
Verify vendor advisory applicability for Red Hat-managed systems.
Monitor DNS service availability and abnormal memory growth after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Reference to Active Allocated Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.