Skip to main content
Mallory
HighVulnerability

CVE-2026-3039: BIND 9 Memory Exhaustion During GSS-API TKEY Negotiation

Published May 20, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 2 in a dayToday
CVSS7.5High · v3.1
EPSS1.1%66th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-3039CWE-400

CVE-2026-3039 is a resource-consumption vulnerability in BIND 9 servers configured for TKEY-based authentication using GSS-API tokens. Processing maliciously constructed packets during GSS-API TKEY negotiation can cause excessive memory consumption and denial of service. Such configurations are commonly used in Active Directory-integrated DNS deployments and Kerberos-secured DNS environments. Affected upstream versions are 9.0.0–9.16.50, 9.18.0–9.18.48, 9.20.0–9.20.22, 9.21.0–9.21.21, 9.9.3-S1–9.16.50-S1, 9.18.11-S1–9.18.48-S1, and 9.20.9-S1–9.20.22-S1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote, unauthenticated attacker can exhaust memory on an affected BIND server, causing denial of service and disrupting DNS availability. The vulnerability has high availability impact; no confidentiality or integrity impact is established.

Mitigation

If you can’t patch tonight, do this now.

Until updates are deployed, restrict network access to affected DNS services to trusted networks wherever operationally feasible, particularly services using TKEY/GSS-API authentication. Monitor BIND memory consumption and service availability to detect resource exhaustion. Access restrictions reduce exposure but do not eliminate the vulnerability for reachable clients.

Remediation

Patch, then assume compromise.

Install the applicable vendor security updates for BIND and its associated packages. Confirm remediation against distribution-specific advisories because patched packages may retain upstream version numbers within the affected ranges. Confirmed corrected packages include RHEL 8 BIND 9.11.36-16.el8_10.8 under RHSA-2026:24339, RHEL 9 BIND 9.16.23-40.el9_8.2 under RHSA-2026:24367, and RHEL 9 bind9.18 9.18.29-14.el9_8.2 under RHSA-2026:24368; later applicable security updates may supersede these builds. Ubuntu installations should apply the fixed bind9 packages specified by USN-8682-1.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Internet Systems ConsortiumBindapplication
FAQ

Frequently asked questions

Is CVE-2026-3039 exploited in the wild?
As of Nov 7, 2026, Mallory has no reports of CVE-2026-3039 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3039?
As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-3039.
Is there a patch for CVE-2026-3039?
Install the applicable vendor security updates for BIND and its associated packages. Confirm remediation against distribution-specific advisories because patched packages may retain upstream version numbers within the affected ranges.
What products are affected by CVE-2026-3039?
Internet Systems Consortium Bind.
How severe is CVE-2026-3039?
CVE-2026-3039 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.1% (66th percentile) as of Nov 7, 2026.
Activity feed

Recent activity

69 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : bind (EulerOS-SA-2026-4628) | Tenable®A memory-exhaustion vulnerability in BIND servers using TKEY authentication with GSS-API tokens, commonly deployed in Active Directory-integrated or Kerberos-secured DNS environments. The advisory identifies affected bind packages in EulerOS Virtualization 2.15.1 and recommends updating them. Nessus checks package versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : bind (EulerOS-SA-2026-4686) | Tenable®A memory-exhaustion vulnerability in BIND servers configured for TKEY authentication using GSS-API tokens, typically in Active Directory-integrated or Kerberos-secured DNS environments. The advisory identifies affected bind packages in EulerOS Virtualization 2.15.0 and recommends updating them. Nessus detects affected versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RHEL 8 : bind (RHSA-2026:95435) | Tenable®Memory exhaustion in BIND 9 during GSS-API TKEY negotiation. The advisory identifies affected RHEL 8 packages and provides security updates.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RHEL 6 : bind (RHSA-2026:95727) | Tenable®A BIND 9 vulnerability causing server memory exhaustion during GSS-API TKEY negotiation. The advisory provides updates for affected RHEL 6 BIND packages. The plugin reports exploit availability for the advisory collectively, without identifying which individual vulnerabilities have exploits.Read more ↗
+44 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.