Skip to main content
Mallory
CriticalVulnerability

CVE-2026-3593: Use-after-free in BIND 9 DNS-over-HTTPS

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.
CVSS9.8Critical · v3.1
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-3593CWE-416 · Use After Free

CVE-2026-3593 is a heap use-after-free read in ISC BIND 9's DNS-over-HTTPS (DoH) HTTP/2 implementation. When HTTP/2 SETTINGS frames modify INITIAL_WINDOW_SIZE while a DoH response is pending, server_read_callback can access the HTTP/2 write buffer after the response/request memory has been released during the write-completion path. The affected ranges are BIND 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and Supported Preview Edition 9.20.9-S1 through 9.20.22-S1. BIND 9.18.x is 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 memory-safety failures in a reachable DoH service, potentially crashing named and denying DNS service. ISC assigned CVSS 3.1 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H). The flaw is a use-after-free read, not a write, and prior claims of arbitrary code execution were withdrawn. The vulnerability has been associated with a potential for disclosure of stale heap contents, but testing described in the available information did not confirm data disclosure because the HTTP/2 library discarded data after end-of-stream had been signaled.

Mitigation

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

Disable DNS-over-HTTPS where it is not operationally required; configurations without DoH enabled are not affected. Until patched, limit exposure of DoH endpoints to authorized clients where feasible and monitor for anomalous bursts or floods of HTTP/2 SETTINGS frames and unexpected named restarts.

Remediation

Patch, then assume compromise.

Upgrade affected deployments to BIND 9.20.23 or later in the 9.20 branch, BIND 9.21.22 or later in the 9.21 branch, or BIND Supported Preview Edition 9.20.23-S1 or later. The fix clears/nulls the HTTP/2 response-buffer state before releasing the underlying request memory, preventing the callback from dereferencing the freed buffer.

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-3593 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-3593 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3593?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-3593.
Is there a patch for CVE-2026-3593?
Upgrade affected deployments to BIND 9.20.23 or later in the 9.20 branch, BIND 9.21.22 or later in the 9.21 branch, or BIND Supported Preview Edition 9.20.23-S1 or later. The fix clears/nulls the HTTP/2 response-buffer state before releasing the underlying request memory, preventing the callback from dereferencing the freed buffer.
What products are affected by CVE-2026-3593?
Internet Systems Consortium Bind.
How severe is CVE-2026-3593?
CVE-2026-3593 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.5% (75th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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

View more in app →
+5 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.