Skip to main content
Mallory
MediumVulnerability

CVE-2026-5947: BIND 9 SIG(0) Validation Use-After-Free

Published May 20, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.9Medium · v3.1
EPSS1.4%73rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-5947CWE-416 · Use After Free

CVE-2026-5947 is a race-condition-induced use-after-free in BIND 9 asynchronous SIG(0) signature validation. When processing a SIG(0)-signed DNS message, BIND initiates asynchronous validation. If the recursive-clients quota is exhausted concurrently, the associated recursive query and DNS message can be discarded while the validation callback still retains and dereferences a pointer to the freed query state. The flaw affects BIND 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and BIND Supported Preview Edition 9.20.9-S1 through 9.20.22-S1. The BIND 9.18.28 through 9.18.49 and corresponding 9.18 Supported Preview Edition releases are not affected.

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 trigger undefined behavior, most notably termination of the named process through a segmentation fault or similar abort, causing denial of service to DNS resolution or authoritative DNS service. Code execution is considered unlikely from the identified improper read, but cannot be categorically excluded for a memory-safety defect.

Mitigation

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

No vendor workaround is available. Until patched, reduce exposure to query-flood conditions by restricting recursive service to authorized clients, applying DNS query rate limiting and upstream DDoS protections, and monitoring for recursive-clients quota exhaustion and unexpected named restarts. These measures reduce exploitability but do not correct the race condition.

Remediation

Patch, then assume compromise.

Upgrade to a fixed BIND release: BIND 9.20.23 or later, BIND 9.21.22 or later, or BIND Supported Preview Edition 9.20.23-S1 or later. The fix retains a reference-counted attachment to the recursive-query object during asynchronous SIG(0) validation and releases it during response-context cleanup, preventing premature object reclamation.

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-5947 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5947 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5947?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5947.
Is there a patch for CVE-2026-5947?
Upgrade to a fixed BIND release: BIND 9.20.23 or later, BIND 9.21.22 or later, or BIND Supported Preview Edition 9.20.23-S1 or later. The fix retains a reference-counted attachment to the recursive-query object during asynchronous SIG(0) validation and releases it during response-context cleanup, preventing premature object reclamation.
What products are affected by CVE-2026-5947?
Internet Systems Consortium Bind.
How severe is CVE-2026-5947?
CVE-2026-5947 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 1.4% (73rd percentile) as of Sep 25, 2026.
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.