Skip to content
OpenAdvisories
Medium SUSE-SU-2026:5118-1 7 CVEs

Security update for bind

Published Nov 5, 2026 · Updated Nov 5, 2026

Summary

This update for bind fixes the following issues:

- CVE-2026-19033: Unauthenticated IXFR deltas are applied to the live zone before TSIG verification (bsc#1280430).
- CVE-2026-19662: qpcache NOQNAME proof use-after-free crashes recursive resolver (bsc#1280432).
- CVE-2026-19668: Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching (bsc#1280436).
- CVE-2026-19941: checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof (bsc#1280437).
- CVE-2026-75029: Message parser retains every identical singleton RDATA, enabling wire-to-work amplification
(bsc#1280438).
- CVE-2026-77119: NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets (bsc#1280440).
- CVE-2026-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).

Fixed packages 1

ReleasePackageFixed in
SUSE · Multi Linux Manager Tools SLE-Micro-5 bind 9.16.6-150000.12.97.1

Vulnerabilities 7

  • Medium 6.5

    Unauthenticated IXFR deltas are applied to the live zone before TSIG verification

    For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signatur…

  • Medium 5.9

    qpcache NOQNAME proof use-after-free crashes recursive resolver

    An attacker may be able to cause a `named` resolver to abort. The attack requires inducing the victim resolver to send multiple queries for a DNSSEC-signed zone hosted by an authoritative server under the control of the attacker. If the auth responds with a p…

  • Medium 5.9

    checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof

    An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 …

  • Medium 5.9

    NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets

    A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure delegation and letting a forged unsigned answer through. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21…

  • Medium 5.8

    Out-of-zone database nodes can become authoritative zone cuts

    A malformed zone may contain an NS or DNAME node above its origin, which `named` treats as a zone cut. If an attacker inserts a malformed zone into a BIND authoritative server (e.g., via zone transfer), queries for names inside the configured zone then lose a…

  • Medium 5.3

    Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching

    A BIND recursive resolver may experience excessive resource consumption if it encounters large numbers of a particular kind of invalid DNSSEC record. Default limits on "max-records-per-type" and "max-types-per-name" help mitigate the exposure. This issue affe…

  • Medium 5.3

    Message parser retains every identical singleton RDATA, enabling wire-to-work amplification

    In a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an SOA record). If the RDATA is the same on all the copies, the record is appended to the in-memory RDATA set, which can cause increased memory …

References

  • report
    https://bugzilla.suse.com/1280430
  • report
    https://bugzilla.suse.com/1280432
  • report
    https://bugzilla.suse.com/1280436
  • report
    https://bugzilla.suse.com/1280437
  • report
    https://bugzilla.suse.com/1280438
  • report
    https://bugzilla.suse.com/1280440
  • report
    https://bugzilla.suse.com/1280442
  • web
    https://www.suse.com/security/cve/CVE-2026-19033
  • web
    https://www.suse.com/security/cve/CVE-2026-19662
  • web
    https://www.suse.com/security/cve/CVE-2026-19668
  • web
    https://www.suse.com/security/cve/CVE-2026-19941
  • web
    https://www.suse.com/security/cve/CVE-2026-75029
  • web
    https://www.suse.com/security/cve/CVE-2026-77119
  • web
    https://www.suse.com/security/cve/CVE-2026-78301