Skip to main content
Mallory
MediumVulnerability

CVE-2026-19668: DNSSEC Validation CPU Exhaustion in ISC BIND 9

Published Sep 16, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days14 mentions · peak 2 in a dayToday
CVSS5.3Medium · v3.1
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-19668CWE-407 · Inefficient Algorithmic Complexity

CVE-2026-19668 is an inefficient algorithmic-complexity vulnerability in ISC BIND 9 recursive resolvers. Processing large numbers of a particular type of invalid DNSSEC record can trigger excessive cryptographic-material matching during DNSSEC validation, consuming excessive CPU resources and potentially disrupting DNS resolution. Affected versions are 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1. Default limits on max-records-per-type and max-types-per-name reduce exposure.

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 attacker can cause excessive resolver CPU consumption, degrading DNS query processing and potentially causing denial of service for clients relying on the resolver. No confidentiality or integrity impact is identified for this vulnerability.

Mitigation

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

Retain the default max-records-per-type and max-types-per-name limits, or restore them if they have been relaxed. These controls limit record quantities and reduce exposure to malicious DNSSEC workloads, but are not identified as a complete substitute for patching.

Remediation

Patch, then assume compromise.

Install vendor security updates explicitly addressing CVE-2026-19668. BIND 9.21.26 includes the fix for the affected 9.21 development series. Distribution fixes include bind9 1:9.20.29-1~deb13u1 or later security-fixed packages for Debian 13. Ubuntu USN-8929-1 supplies release-specific fixes, including 1:9.20.24-1ubuntu0.4 for Ubuntu 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.8 for Ubuntu 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.7 for Ubuntu 22.04 LTS; subsequent security updates supersede these packages. Account for distribution backports rather than relying solely on upstream version comparisons. Migrate end-of-life BIND installations to a supported release series.

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-19668 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-19668 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19668?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-19668.
Is there a patch for CVE-2026-19668?
Install vendor security updates explicitly addressing CVE-2026-19668. BIND 9.21.26 includes the fix for the affected 9.21 development series.
What products are affected by CVE-2026-19668?
Internet Systems Consortium Bind.
How severe is CVE-2026-19668?
CVE-2026-19668 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 0.48% (42nd percentile) as of Nov 6, 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 activity2Community discussion across Reddit, Mastodon, and other social sources.