CVE-2026-80274 PUBLISHED

Validating resolver can abort while caching a mismatched NOQNAME proof

Assigner: isc
Reserved: 26.08.2026 Published: 16.09.2026 Updated: 16.09.2026

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.

Metrics

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

Product Status

Vendor ISC
Product BIND 9
Versions Default: unaffected
  • affected from 9.11.0 to 9.18.50 (incl.)
  • affected from 9.20.0 to 9.20.27 (incl.)
  • affected from 9.21.0 to 9.21.25 (incl.)
  • affected from 9.11.3-S1 to 9.18.50-S1 (incl.)
  • affected from 9.20.9-S1 to 9.20.27-S1 (incl.)

Exploits

We are not aware of any active exploits.

Workarounds

No workarounds known.

Solutions

Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1.

Credits

  • ISC would like to thank hythyt for bringing this vulnerability to our attention.

References

Problem Types

  • CWE-617 Reachable Assertion CWE

Impacts

  • A successful attack could cause an unexpected program exit and denial-of-service.