CVE-2026-19668

DiscoveredSep 16, 2026UpdatedOct 26, 2026

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.

View graph Watch Export

CVSS v3.1

5.3 MEDIUM

EPSS

0.48%

probability of exploitation in 30 days

CISA KEV

Not listed

no confirmed exploitation reported

News coverage

sources referencing this CVE

Related IOCs

seen in the same coverage

Intelligence Reports1

1 intelligence report available

Curated threat research and citations from CrowdStrike, Mandiant, Microsoft, and other sources — unlock with Premium.

Upgrade to Premium

EPSS Trend

Sep 19, 2026 → Oct 6, 2026

▲ 0.08pp

0.40% → 0.48% over 3 tracked changes

CVSS v3.1 Detail

Attack VectorNETWORK

Attack ComplexityLOW

Privileges RequiredNONE

User InteractionNONE

ScopeUNCHANGED

ConfidentialityNONE

IntegrityNONE

AvailabilityLOW

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

Connections

3 relationships

CWE-407

source

Timeline

disclosure → media coverage

Sep 16, 2026

Disclosure — published as a CVE record. · last revised by NVD Oct 26, 2026

Sep 17, 2026

thehackernews.com reports: BIND 9 Update Fixes 14 Flaws, Including an Unauthenticated Crash Over DNS-over-HTTPS

Nov 3, 2026

ubuntu.com reports: USN-8969-1: Bind vulnerabilities