Linux ·
Fedora · Security advisory · November 7, 2026
Fedora · Security advisory · November 7, 2026FEDORA-2026-ABA85B9A89: Security update for 15 packages
FEDORA-2026-ABA85B9A89, released November 7, 2026, fixes 15 CVEs across 15 products. None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
15
None rated Critical
Exploited
0
None reported
Highest CVSS
8.6
Base score, 0 to 10
Highest EPSS
0.0057
47th percentile
Priority of the 15 CVEs
Patch now 0
Urgent 0
High 8
Routine 7
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| bind | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-chroot | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-debuginfo | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-debugsource | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-devel | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-dnssec-utils | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-dnssec-utils-debuginfo | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-doc | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-dyndb-ldap | Fedora 43 | 11.11-15.fc43 |
| bind-dyndb-ldap-debuginfo | Fedora 43 | 11.11-15.fc43 |
| bind-dyndb-ldap-debugsource | Fedora 43 | 11.11-15.fc43 |
| bind-libs | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-libs-debuginfo | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-utils | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
| bind-utils-debuginfo | Fedora 43 | 32:9.18.51^git20261003.d0a87358-2.fc43 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-19666 | Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path | 7.5 | 0.0057 | None reported |
| High | CVE-2026-19667 | Remote assertion failure via 16-bit length truncation in `dns_ncache_add()` | 7.5 | 0.0057 | None reported |
| High | CVE-2026-80274 | Validating resolver can abort while caching a mismatched NOQNAME proof | 7.5 | 0.0057 | None reported |
| High | CVE-2026-81563 | SVCB AliasMode additional-data error leaks qpcache references | 7.5 | 0.0057 | None reported |
| High | CVE-2026-81736 | bind9: If a BIND resolver has cached a tree of SVCB/HTTPS AliasMode records, and is then queried for the root of that tree,... | 7.5 | 0.0057 | None reported |
| High | CVE-2026-19662 | qpcache NOQNAME proof use-after-free crashes recursive resolver | 8.1 | 0.0046 | None reported |
| High | CVE-2026-11331 | Potential wildcard CNAME RPZ policy bypass | 8.6 | 0.0043 | None reported |
| High | CVE-2026-13321 | DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field | 8.6 | 0.0022 | None reported |
| Routine | CVE-2026-19668 | Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching | 5.3 | 0.0048 | None reported |
| Routine | CVE-2026-75029 | libdns-export1100: In a query response, an attacker may send `named` multiple copies of a record that should only exist once (such as an... | 5.3 | 0.0048 | None reported |
| Routine | CVE-2026-10822 | Key Record using PRIVATEDNS algorithm may lead to unexpected exit | 6.5 | 0.0042 | None reported |
| Routine | CVE-2026-19033 | bind9: For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transf... | 6.5 | 0.0024 | None reported |
| Routine | CVE-2026-19941 | checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof | 5.9 | 0.0023 | None reported |
| Routine | CVE-2026-77119 | bind9: A validly signed NSEC3 from an unrelated sibling zone may be accepted as an insecurity proof, downgrading a secure de... | 5.9 | 0.0023 | None reported |
| Routine | CVE-2026-78301 | Out-of-zone database nodes can become authoritative zone cuts | 5.8 | 0.0021 | None reported |
Showing 1 to 15 of 15
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.