Linux ·
openSUSE Leap · Security advisory · July 30, 2026
openSUSE Leap · Security advisory · July 30, 2026OPENSUSE-SU-2026:21489-1: bind security update
OPENSUSE-SU-2026:21489-1, released July 30, 2026, fixes 9 CVEs in bind (version 9.20.26-160000.1.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
9
None rated Critical
Exploited
0
None reported
Highest CVSS
8.6
Base score, 0 to 10
Highest EPSS
0.0067
52nd percentile
Priority of the 9 CVEs
Patch now 0
Urgent 0
High 8
Routine 1
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| bind | opensuse-leap 16.0 | 9.20.26-160000.1.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-11605 | Unnecessary validation of DNSSEC signed records | 7.5 | 0.0067 | None reported |
| High | CVE-2026-11622 | Potential memory usage beyond configured limits | 8.6 | 0.0054 | None reported |
| High | CVE-2026-12617 | Record ordering based unexpected exit with CNAME or DNAME | 7.5 | 0.0052 | None reported |
| High | CVE-2026-13204 | Unexpected exit in certain situations with NSEC and NSEC3 both present | 8.6 | 0.0052 | None reported |
| High | CVE-2026-11331 | Potential wildcard CNAME RPZ policy bypass | 8.6 | 0.0043 | None reported |
| High | CVE-2026-11721 | Cache poisoning possible with label count discrepancy, RRSIG, and wildcards | 8.6 | 0.0040 | None reported |
| High | CVE-2026-10723 | Incorrect acceptance of NSEC3 records | 8.6 | 0.0027 | 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-10822 | Key Record using PRIVATEDNS algorithm may lead to unexpected exit | 6.5 | 0.0042 | None reported |
Showing 1 to 9 of 9
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.