Skip to content
Noroxi
CVE-2026-80274· NVD / CVE Program· CNA isc

Validating resolver can abort while caching a mismatched NOQNAME proof

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.56% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: azl3 bind 9.20.26-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to azl3 bind 9.20.26-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit. 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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 16, 2026
Updated
Sep 17, 2026
EPSS
0.5% · 46th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · isc
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80274

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for isc records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (isc). Independent of NVD's CPE analysis and usually ahead of it.

  • ISC BIND 9

    • 9.11.0 and later · up to and including 9.18.50affected
    • 9.20.0 and later · up to and including 9.20.27affected
    • 9.21.0 and later · up to and including 9.21.25affected
    • 9.11.3-S1 and later · up to and including 9.18.50-S1affected
    • 9.20.9-S1 and later · up to and including 9.20.27-S1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10bindbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-chrootbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-develbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-dnssec-utilsbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-docbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-libsbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-licensebefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:10bind-utilsbefore 32:9.18.33-15.el10_2.1232:9.18.33-15.el10_2.12
AlmaLinux:8bindbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-chrootbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-develbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-export-develbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-export-libsbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-libsbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-libs-litebefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-licensebefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-lite-develbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-pkcs11before 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-pkcs11-develbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-pkcs11-libsbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-pkcs11-utilsbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-sdbbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-sdb-chrootbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16
AlmaLinux:8bind-utilsbefore 32:9.11.36-16.el8_10.1632:9.11.36-16.el8_10.16

+96

Same product

isc: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-12705DNS-over-HTTPS implementation suffers from multiple issues under heavy query load
    36Monitor
  • CVE-2025-40775DNS message with invalid TSIG causes an assertion failure
    35Monitor
  • CVE-2024-11187Many records in the additional section cause CPU exhaustion
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-76163Sep 16, 2026 · named aborts on a TKEY query when the user configuration has no global options statement
    30Monitor
  • ← EarlierCVE-2026-77119Sep 16, 2026 · NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets
    23Monitor
  • Later →CVE-2026-19630Oct 21, 2026 · Amplified resource exhaustion in inbound message processing
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 bind 9.20.26-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:bind32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-chroot32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-devel32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-dnssec-doc32:9.16.23-40.el9_8.10 · AlmaLinux:9Package registry (OSV)
almalinux:bind-dnssec-utils32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-doc32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-libs32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-license32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind-utils32:9.18.33-15.el10_2.12 · AlmaLinux:10Package registry (OSV)
almalinux:bind9.1632:9.16.23-0.22.el8_10.16 · AlmaLinux:8Package registry (OSV)
almalinux:bind9.16-chroot32:9.16.23-0.22.el8_10.16 · AlmaLinux:8Package registry (OSV)
almalinux:bind9.1832:9.18.29-14.el9_8.10 · AlmaLinux:9Package registry (OSV)
almalinux:bind9.18-chroot32:9.18.29-14.el9_8.10 · AlmaLinux:9Package registry (OSV)
almalinux:bind9.18-devel32:9.18.29-14.el9_8.10 · AlmaLinux:9Package registry (OSV)
almalinux:bind9.18-dnssec-utils32:9.18.29-14.el9_8.10 · AlmaLinux:9Package registry (OSV)
almalinux:python3-bind32:9.16.23-40.el9_8.10 · AlmaLinux:9Package registry (OSV)
alpine:bind9.20.29-r0 · Alpine:v3.22Package registry (OSV)
debian:bind91:9.20.29-1~deb13u1 · Debian:13Package registry (OSV)
opensuse:bind9.20.29-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:bind0:9.20.29-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:bind-chroot0:9.20.29-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:bind-debuginfo32:9.18.33-15.el10_2.12 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:bind-debugsource32:9.18.33-15.el10_2.12 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:bind-devel0:9.20.29-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:bind-dnssec-utils0:9.20.29-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:bind-dnssec-utils-debuginfo32:9.18.33-15.el10_2.12 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:bind-doc0:9.20.29-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:bind-libs0:9.20.29-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:bind-libs-debuginfo32:9.18.33-15.el10_2.12 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+7

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-13878238 days apartMalformed BRID/HHIT records can cause named to terminate unexpectedly
    33Monitor
  • CVE-2026-761630 days apartnamed aborts on a TKEY query when the user configuration has no global options statement
    30Monitor
  • CVE-2026-9731335 days apartSpecific RPZ configurations and query patterns may result in an unexpected exit
    30Monitor
  • CVE-2026-1261756 days apartRecord ordering based unexpected exit with CNAME or DNAME
    30Monitor
  • CVE-2026-1320456 days apartUnexpected exit in certain situations with NSEC and NSEC3 both present
    30Monitor
  • CVE-2025-40777427 days apartA possible assertion failure when 'stale-answer-client-timeout' is set to '0'
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records