CVE Tools

CVE-2026-19667

Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Ask IT to check every bind 9 resolver version and whether it can query external authoritative DNS servers.
  2. Upgrade to the matching patched release: 9.20.29, 9.21.26, or 9.20.29-S1.
  3. Restart the DNS service after upgrading and confirm normal DNS lookups work.

What it is

From the CVE record

If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. This issue affects BIND 9 versions 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.

In plain language

Written by AI from the record

If you run bind 9 versions 9.11.0–9.18.50, 9.20.0–9.20.27, 9.21.0–9.21.25, 9.11.3-S1–9.18.50-S1, or 9.20.9-S1–9.20.27-S1, an outsider can take your DNS service offline, so a typical small business should have IT act promptly.

Unauthenticated remote denial of service in bind 9: a malicious authoritative DNS server can trigger 16-bit length truncation in dns_ncache_add(), creating a zero-byte negative-cache entry that aborts named when read.

If you're affected

  • DNS service outage
  • Website access disruption
  • Email delivery disruption
  • Internal network disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS44th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

0 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 44th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

11 events over 1 day, from the signal feeds we watch.

  1. Patch availableworkaround available, record updated
  2. Patch availablepatch available, workaround available, workaround available, published, weakness classified, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for BIND 9, not every advisory. This one: public exploit.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store