Skip to content
VulniPulse
Advisory severityMedium6.8Red Hat Linux

Medium [CVE-2026-10723] Incorrect acceptance of NSEC3 records

This medium-severity Red Hat Linux advisory covers CVE-2026-10723 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-10723 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Get an email when Red Hat Linux publishes the next one.

VulniPulse checks Red Hat Linux's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

Summary

BIND may accept incorrect child-zone NSEC3 records as valid, which could allow an attacker to forge authenticated NXDOMAIN responses. This issue affects BIND 9 versions 9.18.0 through 9.18.50, 9.20.0 through 9.20.24, 9.21.0 through 9.21.23, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.24-S1.

Exploitation requires high attack complexity, limiting the immediate risk to Red Hat products. Red Hat severity: Moderate — CVSS 6.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N).

Weakness: CWE-345.

Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 7 Extended Lifecycle Support; Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support; Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On; and 15 more.

Affected versions
  • 9.18.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 16 hours 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
  • bind9.16-32:9.16.23-0.7.el8_6.11
  • bind9.16-32:9.16.23-0.14.el8_8.9
  • 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
  • openshift/ose-rhel-coreos-9:416.94.202609011112-0
  • openshift/ose-rhel-coreos-9:417.94.202609191027-0
  • openshift/ose-rhel-coreos-9:418.94.202609031320-0
  • openshift/ose-rhel-coreos-9:4.19.9.6.202610241701-0
  • openshift/ose-rhel-coreos-9:4.20.9.6.202610242033-0
  • openshift/ose-rhel-coreos-9:4.21.9.6.202610241345-0
  • openshift/ose-rhel-coreos-9:4.22.9.8.202608251819-0
  • bind-main-9.20.26-0.1.hum1
  • RHSA-2026:55437
  • RHSA-2026:60383
  • RHSA-2026:54509
  • RHSA-2026:54654
  • RHSA-2026:80501
  • RHSA-2026:79160
  • RHSA-2026:54510
  • RHSA-2026:55442
  • RHSA-2026:57189
  • RHSA-2026:55441
  • RHSA-2026:62549
  • RHSA-2026:70586
  • RHSA-2026:65851
  • RHSA-2026:89651
  • RHSA-2026:89333
  • RHSA-2026:89232
  • RHSA-2026:60440
  • RHSA-2026:54071

Official advisory · high-confidence parse· fetched 16 hours 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, bind9.16-32:9.16.23-0.7.el8_6.11, bind9.16-32:9.16.23-0.14.el8_8.9. That is the remediation for this advisory.

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

Official advisory · high-confidence parse· fetched 16 hours ago·verify at source

All Red Hat Linux advisories

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 34 official vendor sources and 160+ reviewed platform categories.

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.