Skip to main content
Mallory
HighVulnerability

CVE-2026-3104: BIND 9 DNSSEC Proof-of-Non-Existence Memory Leak

Published Mar 25, 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.
CVSS7.5High · v3.1
EPSS0.73%55th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-3104CWE-772 · Missing Release of Resource after…

CVE-2026-3104 is a remotely triggerable memory leak in BIND 9 resolver cache processing for DNSSEC proofs of non-existence. Error paths in the addnoqname() and addclosest() routines fail to release allocated cache objects when an NSEC record is accepted but its associated RRSIG record set exceeds the configured maximum records per type. Subsequent error propagation can also bypass cleanup of a newly allocated cache header. Repeated recursive queries can therefore cause unbounded resolver memory growth. Affected releases are BIND 9.20.0 through 9.20.20, 9.21.0 through 9.21.19, and Supported Preview Edition 9.20.9-S1 through 9.20.20-S1. BIND 9.18 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.

An unauthenticated remote attacker can exhaust memory in an affected recursive resolver, causing DNS lookup failures and denial of service. In reported testing, memory consumption increased linearly with malicious queries; the resulting allocation imbalance may additionally cause named to terminate with an assertion failure during shutdown or reload.

Mitigation

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

No reliable workaround is available. Disabling DNSSEC does not prevent exploitation. Until patched, restrict recursive service to trusted clients, avoid exposing recursive resolvers to untrusted networks, and monitor resolver memory consumption, SERVFAIL rates, and unexpected named restarts or reload failures. Resource limits and service supervision may reduce operational impact but do not eliminate the leak.

Remediation

Patch, then assume compromise.

Upgrade affected installations to BIND 9.20.21 or later in the 9.20 branch, or BIND 9.21.20 or later in the 9.21 branch. Supported Preview Edition deployments should update to a release containing the corresponding fix. Distribution-maintained packages should be updated to the vendor version incorporating these fixed upstream releases.

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-3104 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-3104 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-3104?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-3104.
Is there a patch for CVE-2026-3104?
Upgrade affected installations to BIND 9.20.21 or later in the 9.20 branch, or BIND 9.21.20 or later in the 9.21 branch. Supported Preview Edition deployments should update to a release containing the corresponding fix.
What products are affected by CVE-2026-3104?
Internet Systems Consortium Bind.
How severe is CVE-2026-3104?
CVE-2026-3104 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.73% (55th 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 activity14Community discussion across Reddit, Mastodon, and other social sources.