Skip to main content
Mallory
HighVulnerability

CVE-2026-19667: BIND 9 Negative-Cache Length Truncation Denial of Service

Published Sep 16, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days29 mentions · peak 6 in a dayToday
CVSS7.5High · v3.1
EPSS0.57%48th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-19667CWE-197 · Numeric Truncation Error

CVE-2026-19667 is a numeric truncation vulnerability in BIND 9 named's DNS negative-cache handling. An attacker-controlled authoritative DNS server can supply a negative answer exactly 65,536 bytes long, causing its length to truncate to zero in a 16-bit representation and creating a zero-byte negative cache entry. When named subsequently reads that entry, it aborts. Affected upstream 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. Distribution packages may contain backported fixes despite retaining an affected upstream version number.

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.

Successful exploitation terminates the named process, causing denial of service and interrupting DNS resolution for dependent clients until service is restored. No confidentiality or integrity impact is identified for this vulnerability.

Mitigation

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

No specific vendor workaround is identified. Where operationally feasible, limit exposure to attacker-controlled authoritative DNS responses until patched packages can be deployed; this is not a substitute for the security update.

Remediation

Patch, then assume compromise.

Install the applicable vendor security update for BIND and associated packages. The correction rejects oversized negative-cache records that cannot fit in a dns_rdata_t before they enter the cache. Fixed distribution builds include Debian 12 bind9 1:9.18.49-1~deb12u3, Debian 13 bind9 1:9.20.29-1~deb13u1, RHEL 9.6 bind9.18 9.18.29-4.el9_6.5 under RHSA-2026:94278, and RHEL 10.0 bind 9.18.33-4.el10_0.6 under RHSA-2026:94115. Use the full distribution package version and product-specific advisory to verify remediation rather than relying solely on the upstream version.

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-19667 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-19667 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19667?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-19667.
Is there a patch for CVE-2026-19667?
Install the applicable vendor security update for BIND and associated packages. The correction rejects oversized negative-cache records that cannot fit in a dns_rdata_t before they enter the cache.
What products are affected by CVE-2026-19667?
Internet Systems Consortium Bind.
How severe is CVE-2026-19667?
CVE-2026-19667 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.57% (48th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

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

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