Skip to content
VulniPulse
High7.5Red Hat Linux

High [CVE-2026-13204] Unexpected exit with NSEC and NSEC3 both present

This high-severity Red Hat Linux advisory covers CVE-2026-13204 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8.

CVE-2026-13204 Published Jul 22, 2026Updated by vendor Jul 22, 2026
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

If a provably insecure domain is covered by both an NSEC and NSEC3 record at the parent, and there exist an RRSIG for only one of these types, then BIND may exit unexpectedly with an assertion while validating this proof. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Weakness: CWE-617.

Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 7 Extended Lifecycle Support; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions; Red Hat Enterprise Linux 9.6 Extended Update Support; Red Hat OpenShift Container Platform 4.22; Red Hat Hardened Images; Red Hat Enterprise Linux 6.

Red Hat lists Red Hat Enterprise Linux 9 as not affected. Red Hat fixing advisory: RHSA-2026:55437, RHSA-2026:60383, RHSA-2026:54509, RHSA-2026:54654, RHSA-2026:54510, RHSA-2026:55442, RHSA-2026:57189, RHSA-2026:55441, RHSA-2026:57362, RHSA-2026:54071.

Affected products named by the advisory: Red Hat package: bind9.16; Red Hat package: bind9.18.

Affected versions
  • 9.11.0
  • 9.18.50
  • 9.20.0
  • 9.20.24
  • 9.21.0
  • 9.21.23
  • 9.11.3
  • 9.20.9

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Fixed versions
  • bind-32:9.18.33-15.el10_2.10
  • bind-32:9.11.4-26.P2.el7_9.21
  • bind9.16-32:9.16.23-0.22.el8_10.12
  • bind-32:9.11.36-16.el8_10.14
  • bind-32:9.16.23-40.el9_8.8
  • bind9.18-32:9.18.29-14.el9_8.8
  • bind-32:9.16.23-18.el9_4.12
  • bind-32:9.16.23-31.el9_6.4
  • rhcos-4.22.9.8.202608191915-0
  • bind-main-9.20.26-0.1.hum1
  • RHSA-2026:55437
  • RHSA-2026:60383
  • RHSA-2026:54509
  • RHSA-2026:54654
  • RHSA-2026:54510
  • RHSA-2026:55442
  • RHSA-2026:57189
  • RHSA-2026:55441
  • RHSA-2026:57362
  • RHSA-2026:54071

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Mitigation

Upgrade to a fixed release: bind-32:9.18.33-15.el10_2.10, bind-32:9.11.4-26.P2.el7_9.21, bind9.16-32:9.16.23-0.22.el8_10.12, bind-32:9.11.36-16.el8_10.14, bind-32:9.16.23-40.el9_8.8, bind9.18-32:9.18.29-14.el9_8.8. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.