Linux · SUSE Linux Enterprise · Security advisory · November 7, 2026
SUSE-SU-2026:4620-1: unbound security update
SUSE-SU-2026:4620-1, released November 7, 2026, fixes 10 CVEs in unbound (version 1.26.1-150600.23.24.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
10
None rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0096
61st percentile
Priority of the 10 CVEs
Patch now 0
Urgent 0
High 5
Routine 5
Fixed package versions
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-81642 | Heap buffer overflow and possible Remote Code Execution when digesting DNSKEY | 9.8 | 0.0096 | None reported |
| High | CVE-2026-82717 | CNAME synthesis could lead to heap corruption | 9.8 | 0.0078 | None reported |
| High | CVE-2026-80225 | Possible degradation of service from continuous queries on the same TCP/DoT connection | 7.5 | 0.0048 | None reported |
| High | CVE-2026-85501 | Retrap: Novel Vulnerabilities to launch Algorithmic Complexity Attacks on DNSSEC | 7.5 | 0.0048 | None reported |
| High | CVE-2026-81634 | Possible heap buffer overflow during DNSSEC canonicalization | 9.8 | 0.0048 | None reported |
| Routine | CVE-2026-82720 | Use-after-free in DoH stream cleanup code path | 5.9 | 0.0038 | None reported |
| Routine | CVE-2026-78227 | Use-after-free in DoQ stream output buffer on reset re-transmission | 6.5 | 0.0034 | None reported |
| Routine | CVE-2026-77860 | 'serve-expired' can bypass Unbound 'wait-limit' | 3.7 | 0.0030 | None reported |
| Routine | CVE-2026-77955 | unbound: Possible ZONEMD verification bypass window (bsc#1280404). | 4.4 | 0.0017 | None reported |
| Routine | CVE-2026-50248 | BOGUS configured primary hostname accepted for XFR in auth/rpz zones | 6.5 | 0.0013 | None reported |
Showing 1 to 10 of 10
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.