Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (CVE-2026-19668) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-19668

Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching

Answer in brief

CVE-2026-19668 records a Unknown severity vulnerability in Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching. The current sources do not mark it as known exploited. The current feed maps ISC/BIND 9 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ISC/BIND 9 (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ISC/BIND 9generic	9.11.0 \|\| 9.20.0 \|\| 9.21.0 \|\| 9.11.3-S1 \|\| 9.20.9-S1	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for ISC/BIND 9.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source description

A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular kind of invalid DNSSEC record. Default limits on "max-records-per-type" and "max-types-per-name" help mitigate the exposure. 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.

Quoted source text, attributed separately from HOL analysis.