Skip to main content
Mallory
MediumVulnerability

CVE-2026-19941: Forged DNSSEC-Validated NXDOMAIN Responses in BIND 9

Published Sep 16, 2026 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days16 mentions · peak 3 in a dayToday
CVSS5.9Medium · v3.1
EPSS0.23%13th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Internet Systems Consortium
IdentifiersCVE-2026-19941CWE-345 · Insufficient Verification of Data…

CVE-2026-19941 is a DNSSEC denial-of-existence validation vulnerability in BIND 9's named resolver. The resolver may accept an inapplicable NSEC record as proof that no wildcard exists, allowing an attacker at the same or an upstream level of the zone name to conceal a victim's wildcard record through forged DNSSEC-validated NXDOMAIN responses. Affected upstream versions are 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, and 9.20.9-S1–9.20.27-S1. Distribution packages may contain backported fixes despite retaining an upstream version within these ranges.

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 compromises DNS resolution integrity by causing a validating resolver to report nonexistence for names that should resolve through a wildcard record. Clients can consequently receive apparently DNSSEC-validated negative answers that conceal legitimate wildcard-based DNS data. The vulnerability-specific CVSS assessment identifies high integrity impact and no confidentiality or availability impact; arbitrary code execution, privilege escalation, and resolver crashes are not established for this vulnerability.

Mitigation

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

No vulnerability-specific temporary workaround is documented. Where a fix is pending or in QA, track the vendor's release status rather than treating unreleased candidate packages as completed remediation.

Remediation

Patch, then assume compromise.

Install the vendor security update explicitly addressing CVE-2026-19941. Identified fixes include BIND 9.21.26 in Fedora bind9-next updates and Debian 12 bind9 package 1:9.18.49-1~deb12u3. Ubuntu corrected packages include 1:9.20.24-1ubuntu3.1 for 26.10, 1:9.20.24-1ubuntu0.5 for 26.04 LTS, 1:9.18.39-0ubuntu0.24.04.9 for 24.04 LTS, and 1:9.18.39-0ubuntu0.22.04.8 for 22.04 LTS. For SUSE and other distributions, use the released fixed package for the installed product and support channel. Assess distribution package release numbers rather than upstream versions alone. Fedora candidates still pending testing or release approval should not be treated as available stable updates. Migrate unsupported installations to a supported, patched release.

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-19941 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2026-19941 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19941?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2026-19941.
Is there a patch for CVE-2026-19941?
Install the vendor security update explicitly addressing CVE-2026-19941. Identified fixes include BIND 9.21.26 in Fedora bind9-next updates and Debian 12 bind9 package 1:9.18.49-1~deb12u3.
What products are affected by CVE-2026-19941?
Internet Systems Consortium Bind.
How severe is CVE-2026-19941?
CVE-2026-19941 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 0.23% (13th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

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

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