Skip to main content
Mallory
HighVulnerability

CVE-2026-19630: Denial of Service in BIND 9 DNS Message Processing

Published Oct 21, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days83 mentions · peak 12 in a dayToday
CVSS7.5High · v3.1
EPSS0.45%39th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-19630CWE-407 · Inefficient Algorithmic Complexity

CVE-2026-19630 is a resource-exhaustion vulnerability in ISC BIND 9 resolvers. Specially structured inbound DNS messages trigger additional processing without an enforced limit. Messages containing maliciously large numbers of the triggering structures cause disproportionate CPU and memory consumption during parsing, potentially denying DNS service. 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. The specific triggering structures and vulnerable function are not identified.

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.

Exploitation can exhaust resolver CPU and memory, degrade DNS query processing, and cause denial of service for clients relying on the affected resolver. The vulnerability has high availability impact; confidentiality and integrity impacts are not identified.

Mitigation

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

No confirmed vulnerability-specific workaround is identified. As interim risk reduction, restrict resolver access to authorized clients where operationally appropriate and monitor CPU and memory consumption. Access restrictions may reduce exposure but are not a confirmed defense against all delivery paths and do not correct the processing flaw.

Remediation

Patch, then assume compromise.

Install a vendor security update explicitly addressing CVE-2026-19630. Fixed upstream releases include BIND 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1. Distribution-maintained installations should use the applicable vendor-fixed package, which may contain backported fixes. Debian trixie identifies 1:9.20.30-1~deb13u1 as fixed, and Debian unstable identifies 1:9.20.30-1. Security updates are also identified for affected Ubuntu, Red Hat, Rocky Linux, Fedora, TencentOS, and MiracleLinux packages.

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-19630 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-19630 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19630?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-19630.
Is there a patch for CVE-2026-19630?
Install a vendor security update explicitly addressing CVE-2026-19630. Fixed upstream releases include BIND 9.20.30, 9.21.27, and Supported Preview Edition 9.20.30-S1.
What products are affected by CVE-2026-19630?
Internet Systems Consortium Bind.
How severe is CVE-2026-19630?
CVE-2026-19630 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.45% (39th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

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

View more in app →
+65 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 activity10Community discussion across Reddit, Mastodon, and other social sources.