Skip to content
OpenAdvisories
High RHSA-2026:54071 8 CVEs

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Published Aug 12, 2026 · Updated Nov 13, 2026

Fixed packages 7

ReleasePackageFixed in
Red Hat · Hardened Images 1 hummingbird:1 bind 32:9.20.26-0.1.hum1
Red Hat · Hardened Images 1 hummingbird:1 bind-chroot 32:9.20.26-0.1.hum1
Red Hat · Hardened Images 1 hummingbird:1 bind-devel 32:9.20.26-0.1.hum1
Red Hat · Hardened Images 1 hummingbird:1 bind-dnssec-utils 32:9.20.26-0.1.hum1
Red Hat · Hardened Images 1 hummingbird:1 bind-doc 32:9.20.26-0.1.hum1
Red Hat · Hardened Images 1 hummingbird:1 bind-libs 32:9.20.26-0.1.hum1
Red Hat · Hardened Images 1 hummingbird:1 bind-utils 32:9.20.26-0.1.hum1

Vulnerabilities 8

  • High 8.6

    DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field

    The BIND resolver accepts validly-signed NSEC records where the "Next Domain Name" field points outside the signer's zone. This issue affects BIND 9 versions 9.11.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,…

  • High 7.5

    Potential wildcard CNAME RPZ policy bypass

    An attacker who knows (or guesses) that a resolver uses RPZ with wildcard CNAME policies can craft query names long enough to trigger a NAMETOOLONG error condition during RPZ processing. This is not handled correctly and may lead to defeating the RPZ rule. It…

  • High 7.5

    Potential memory usage beyond configured limits

    A DNSSEC validating resolver that is under a random subdomain attack against a DNSSEC-signed zone can suffer from runaway memory usage. The attacker needs to be able to send queries faster than the resolver can perform validation. The increased memory usage c…

  • High 7.5

    Cache poisoning possible with label count discrepancy, RRSIG, and wildcards

    It is possible for an attacker's zone to respond to a query with an RRSIG that has a smaller number of labels than the zone in which the RRSIG is contained. This causes `named` to produce a wildcard name for a zone that is shorter than the attacker's zone, wh…

  • High 7.5

    Record ordering based unexpected exit with CNAME or DNAME

    The issue is unexpected program termination based on ordering and/or specific content in responses to queries for CNAME or DNAME, and A records. Specifically, if a client queries for a DNAME and A record below the DNAME to the resolver, and the authoritative …

  • High 7.5

    Unexpected exit in certain situations with NSEC and NSEC3 both present

    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. This issue affects BIND 9 versions 9.…

  • Medium 6.8

    Incorrect acceptance of NSEC3 records

    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 …

  • Medium 6.5

    Key Record using PRIVATEDNS algorithm may lead to unexpected exit

    If BIND encounters a particular invalid data structure in a DNS record, it will accept the invalid data, and may subsequently abort and exit. BIND will first need to store a DNS record for a key (KEY, DNSKEY, etc.). That key must specify a PRIVATEDNS algorith…

References

  • report
    https://access.redhat.com/security/cve/CVE-2026-11721
  • article
    https://access.redhat.com/security/updates/classification/
  • article
    https://images.redhat.com/
  • report
    https://access.redhat.com/security/cve/CVE-2026-10822
  • report
    https://access.redhat.com/security/cve/CVE-2026-10723
  • report
    https://access.redhat.com/security/cve/CVE-2026-13204
  • report
    https://access.redhat.com/security/cve/CVE-2026-12617
  • report
    https://access.redhat.com/security/cve/CVE-2026-11622
  • report
    https://access.redhat.com/security/cve/CVE-2026-13321
  • report
    https://access.redhat.com/security/cve/CVE-2026-11331
  • advisory
    https://security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_54071.json
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504560
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-10723
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-10723
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504598
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-10822
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-10822
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2503721
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-11331
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-11331
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504298
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-11622
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-11622
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504338
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-11721
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-11721
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504370
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-12617
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-12617
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504447
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-13204
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-13204
  • report
    https://bugzilla.redhat.com/show_bug.cgi?id=2504166
  • advisory
    https://www.cve.org/CVERecord?id=CVE-2026-13321
  • advisory
    https://nvd.nist.gov/vuln/detail/CVE-2026-13321