RHSA-2026:25214HighCVSS 7.5

Red Hat Security Advisory: bind security update

Published
June 11, 2026
Last Modified
August 24, 2026

🔗 CVE IDs covered (1)

CVE-2026-1519 →

📋 Description

CVE-2026-1519 — bind: BIND: Denial of Service via maliciously crafted DNSSEC-validated zone

🎯 Affected products45

  • Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-32:9.16.23-18.el9_4.11.src as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-32:9.16.23-18.el9_4.11.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-chroot-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-chroot-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-chroot-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-chroot-32:9.16.23-18.el9_4.11.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debuginfo-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debuginfo-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debuginfo-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debuginfo-32:9.16.23-18.el9_4.11.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debugsource-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debugsource-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debugsource-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-debugsource-32:9.16.23-18.el9_4.11.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-doc-32:9.16.23-18.el9_4.11.noarch as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-32:9.16.23-18.el9_4.11.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-debuginfo-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-debuginfo-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-debuginfo-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-dnssec-utils-debuginfo-32:9.16.23-18.el9_4.11.x86_64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-libs-32:9.16.23-18.el9_4.11.aarch64 as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-libs-32:9.16.23-18.el9_4.11.ppc64le as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • bind-libs-32:9.16.23-18.el9_4.11.s390x as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • +15 more not shown

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate this issue, disable DNSSEC validation on affected BIND resolvers. Alternatively, configure the BIND server as authoritative-only if recursive queries are not required. Disabling DNSSEC validation may reduce the security posture of the DNS resolver. A restart of the BIND service (`named`) is required for these changes to take effect and may temporarily interrupt DNS resolution.

🔗 References (4)