Skip to main content
Mallory
HighVulnerability

CVE-2026-80274: BIND 9 Resolver Denial of Service via Mixed NSEC and NSEC3 Wildcard Proofs

Published Sep 16, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days32 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-80274CWE-20

CVE-2026-80274 is a DNSSEC response-handling vulnerability in ISC BIND 9 resolvers. When a resolver queries a DNSSEC-signed authoritative zone, a response containing a valid wildcard answer and signed NSEC3 proof followed by an unsigned NSEC record at the same owner name can trigger an unexpected program exit. 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. Successful exploitation causes denial of service.

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 terminate an affected BIND resolver, interrupting DNS resolution for clients and services that depend on it. Availability impact is high. No confidentiality or integrity impact is identified for this vulnerability, and arbitrary code execution or cache poisoning is not established.

Mitigation

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

No vulnerability-specific temporary workaround is established. Restrict recursive-query access to trusted clients where feasible, limit unnecessary DNS exposure, and monitor resolver exits and service availability. These measures reduce exposure or aid detection but do not prevent exploitation if an allowed query causes the resolver to process the crafted authoritative response.

Remediation

Patch, then assume compromise.

Install the applicable vendor security update for BIND and associated installed packages. Corrected upstream releases identified include BIND 9.20.29, 9.21.26, and Supported Preview Edition 9.20.29-S1, or later security-fixed releases. Distribution-specific corrected builds include Debian 12 bind9 1:9.18.49-1~deb12u3, RHEL 10.0 BIND 9.18.33-4.el10_0.6, and RHEL 9.6 bind9.18 9.18.29-4.el9_6.5. Assess distribution packages using their complete version-release identifiers because backported fixes may retain upstream version numbers within the affected ranges. Migrate unsupported installations to a maintained 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-80274 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-80274 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-80274?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2026-80274.
Is there a patch for CVE-2026-80274?
Install the applicable vendor security update for BIND and associated installed packages. Corrected upstream releases identified include BIND 9.20.29, 9.21.26, and Supported Preview Edition 9.20.29-S1, or later security-fixed releases.
What products are affected by CVE-2026-80274?
Internet Systems Consortium Bind.
How severe is CVE-2026-80274?
CVE-2026-80274 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

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

View more in app →
tenable nessus pluginsNews · Nov 14, 2026Rocky Linux 9.6 [CIQ] Security Update: bind9.18 / bind9.18-chr... | Tenable®A vulnerability covered by the aggregated bind9.18 security update for Rocky Linux 9.6. The content provides no individual technical details or CVE-specific exploitation status.Read more ↗tenable nessus pluginsNews · Nov 9, 2026Unity Linux 20.1070e Security Update: bind (UTSA-2026-150956) | Tenable®A remotely triggerable denial-of-service vulnerability in BIND causes a resolver to exit unexpectedly when processing a particular DNSSEC response sequence. Affected 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. The advisory assigns a CVSS v3 base score of 7.5. Unity Linux provides an affected bind package update under UTSA-2026-150956. Nessus identifies exposure using the application's self-reported version rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RHEL 7 : bind (RHSA-2026:95726) | Tenable®A denial-of-service vulnerability in BIND triggered by a crafted DNSSEC reply. The advisory identifies affected BIND packages on Red Hat Enterprise Linux 7 and provides security updates. Nessus checks package versions rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 6, 2026RHEL 8 : bind (RHSA-2026:95435) | Tenable®A denial-of-service vulnerability in BIND triggered by a crafted DNSSEC reply. Security updates are available for affected RHEL 8 packages.Read more ↗
+78 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 activity5Community discussion across Reddit, Mastodon, and other social sources.