Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-94300: Potential remote code execution in BIND 9 through GSS-TSIG UDP replay

Published Oct 21, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days129 mentions · peak 35 in a dayToday
CVSS8.1High · v3.1
EPSS0.95%62nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-94300CWE-415 · Double Free

CVE-2026-94300 is a memory-corruption vulnerability in the BIND 9 DNS server's handling of concurrent GSS-TSIG messages. Improperly serialized access to shared GSS-TSIG security contexts can cause a double free. An attacker who captures a GSS-TSIG-signed UDP message can replay it while the negotiated TSIG key remains valid, potentially terminating the server. Combining replay with crafted queries involving an attacker-controlled zone may enable remote code execution. Affected versions are 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.

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.

Successful exploitation can corrupt DNS server memory and terminate the process, disrupting DNS service. Under additional attack conditions, remote arbitrary code execution may compromise confidentiality, integrity, and availability within the server process's security context. Exploitation has high complexity and requires neither existing privileges nor user interaction.

Mitigation

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

No vulnerability-specific temporary workaround is established. Apply the applicable vendor security update.

Remediation

Patch, then assume compromise.

Install vendor-provided BIND security updates. Fixed upstream releases include 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1; use these or later fixed releases in the corresponding branches. For distribution-maintained installations, apply the applicable security advisory's corrected packages, which may contain backported fixes without changing to these upstream version numbers.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-94300This is a standalone research lab, not a recognized exploit-framework module. Its 27 files comprise 12 English/German Markdown documents, six Python files, one C shim, two POSIX shell scripts, one Dockerfile, and five configuration/zone files. The code-file count includes the Dockerfile; shell files use /bin/sh despite being grouped under bash in the language list. host/exploit.py is the main host entry point. It discovers a local Docker container, reads LEAK records from docker logs, validates supplied addresses and packet metadata, stages an operator command through docker exec, sends the captured signed DNS packet over UDP, and checks execution evidence. lab/rce_victim.sh bootstraps Kerberos and named, compiles/preloads the shim, starts gdb with ASLR disabled, captures a signed packet without transmitting it, publishes debugger-derived addresses, and waits for host replay. rce_model.py loads separate leak and exploit stages. rce_exploit.py constructs fake database/method objects and models a corrupt key pointer; rce_shim.c intercepts the selected free, installs replacement contents, and supplies the command-execution function. Separate protocol tools provide TKEY negotiation, concurrent identical or DNS-ID-modified packet replay, reload testing, optional signed updates, and heap-grooming experiments. The repository attributes use-after-free/double-free behavior to unsynchronized operations on a shared GSS-TSIG context. It also describes a separate destructive keyring-dump/reload defect. The claimed replay trigger needs a captured packet associated with a still-live context, rather than arbitrary unauthenticated DNS traffic. The supplied RCE demonstration does not establish remote exploitation: addresses come from gdb, corruption/object control is injected, and the shim writes fake contents even if allocation does not return the freed target chunk. Commands arrive over an already-authorized Docker control channel, not DNS. The preloaded payload executes with named's existing privileges, writes proof, and exits; no container escape, persistence, or built-in callback is identified. OPERATIONAL describes the supplied model payload only, not a working remote RCE chain. The documentation claims affected version ranges and fixes in 9.20.30/9.21.27, but advisory authenticity, runtime measurements, and those version claims were not independently verified. Several supplied files are truncated, and referenced external reports/logs are absent. The repository itself warns that substantial AI assistance was used. No evidence of a deceptive fake exploit was identified, but its model boundaries must be retained. Original repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.Ibonok · Disclosed Oct 23, 2026 · python · c · network · localOperational
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-94300 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-94300 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-94300?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-94300, the earliest disclosed Oct 23, 2026.
Is there a patch for CVE-2026-94300?
Install vendor-provided BIND security updates. Fixed upstream releases include 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1; use these or later fixed releases in the corresponding branches.
What products are affected by CVE-2026-94300?
Internet Systems Consortium Bind.
How severe is CVE-2026-94300?
CVE-2026-94300 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.95% (62nd percentile) as of Nov 17, 2026.
Activity feed

Recent activity

129 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 16, 2026RockyLinux 10 : bind (RLSA-2026:98637) | Tenable®A BIND vulnerability allowing arbitrary code execution through GSS-TSIG UDP message replay. The advisory identifies affected packages on RockyLinux 10 and recommends updating them. The plugin reports that exploits are available, without distinguishing availability for individual vulnerabilities.Read more ↗tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 9 [CIQ] Security Update: bind / bind-chroot / bind... | Tenable®A BIND arbitrary-code-execution vulnerability involving replay of GSS-TSIG UDP messages, affecting packages on Rocky Linux 9. The associated CVSS vector describes network exploitation with high attack complexity, no required privileges or user interaction, and high confidentiality, integrity, and availability impacts. The listing reports available exploits and includes a proof-of-concept exploit-maturity value in its temporal vector; it does not report exploitation in the wild.Read more ↗tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 9 [CIQ] Security Update: bind9.18 / bind9.18-chroo... | Tenable®An arbitrary-code-execution vulnerability in BIND involving replay of GSS-TSIG UDP messages. The advisory identifies affected packages on Rocky Linux 9. The plugin reports exploits are available and supplies a proof-of-concept temporal metric for the score sourced to this CVE; it does not report exploitation in the wild.Read more ↗tenable nessus pluginsNews · Nov 13, 2026RockyLinux 9 : bind (RLSA-2026:98497) | Tenable®A BIND vulnerability allowing arbitrary code execution through GSS-TSIG UDP message replay. The supplied CVSS vector describes network exploitation with high attack complexity, no required privileges or user interaction, and high confidentiality, integrity, and availability impacts. Security updates are available through RLSA-2026:98497.Read more ↗
+67 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 activity52Community discussion across Reddit, Mastodon, and other social sources.