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-19666: Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path (bsc#1280433).
- CVE-2026-19667: Remote assertion failure via 16-bit length truncation in dns_ncache_add() (bsc#1280435).
- 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-78301: Out-of-zone database nodes can become authoritative zone cuts (bsc#1280442).
- CVE-2026-80274: Validating resolver can abort while caching a mismatched NOQNAME proof (bsc#1280443).
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 12 SP5 Linux Enterprise Server 12 SP5-LTSS | bind | 9.11.22-3.77.1 |
| SUSE · SLES 12 SP5 Linux Enterprise Server LTSS Extended Security 12 SP5 | bind | 9.11.22-3.77.1 |
Vulnerabilities 8
-
High 7.5
Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path
On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.2…
-
High 7.5
Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`
If an attacker-controlled authoritative server can produce a negative answer that is exactly 65536 bytes, then a flaw in `named` results in a negative cache entry of 0 bytes. When this entry is subsequently read, `named` aborts. This issue affects BIND 9 vers…
-
High 7.5
Validating resolver can abort while caching a mismatched NOQNAME proof
If a BIND resolver sends a query for a DNSSEC-signed authoritative zone, and the authoritative server replies with a valid wildcard answer and signed NSEC3 proof, followed by an unsigned NSEC at the same owner name, it will trigger an unexpected program exit.…
-
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.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
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/1280433
-
report
https://bugzilla.suse.com/1280435
-
report
https://bugzilla.suse.com/1280437
-
report
https://bugzilla.suse.com/1280438
-
report
https://bugzilla.suse.com/1280442
-
report
https://bugzilla.suse.com/1280443
-
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-19666
-
web
https://www.suse.com/security/cve/CVE-2026-19667
-
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-78301
-
web
https://www.suse.com/security/cve/CVE-2026-80274