Linux ·
openSUSE Leap · Security advisory · November 7, 2026
openSUSE Leap · Security advisory · November 7, 2026OPENSUSE-SU-2026:22076-1: Security update for 3 packages
OPENSUSE-SU-2026:22076-1, released November 7, 2026, fixes 243 CVEs across 3 products. 2 of them are being exploited (CVE-2025-6558); 2 on CISA KEV. Patch Radar priority: Patch now.
Patch now2 on CISA KEV
CVEs closed
243
44 rated Critical
Exploited
2
CVE-2025-6558
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.2162
97th percentile
Priority of the 243 CVEs
Patch now 2
Urgent 44
High 194
Routine 3
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| webkit2gtk3 | opensuse-leap 16.0 | 2.54.1-160000.1.1 |
| webkit2gtk3-soup2 | opensuse-leap 16.0 | 2.54.1-160000.1.1 |
| webkit2gtk4 | opensuse-leap 16.0 | 2.54.1-160000.1.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Patch now | CVE-2025-6558 | Chromium: CVE-2025-6558 Incorrect validation of untrusted input in ANGLE and GPU | 8.8 | 0.1093 | KEVExploited |
| Patch now | CVE-2026-3909 | Chromium: CVE-2026-3909 Out of bounds write in Skia | 9.6 | 0.0233 | KEVExploited |
| Urgent | CVE-2024-1283 | Chromium: CVE-2024-1283 Heap buffer overflow in Skia | 9.8 | 0.2162 | None reported |
| Urgent | CVE-2024-43091 | webkit2gtk3: This update for webkit2gtk3 fixes the following issues: Security issues fixed: WebKitGTK and WPE WebKit Security Ad... | 9.8 | 0.0073 | None reported |
| Urgent | CVE-2026-10881 | Chromium: CVE-2026-10881 Out of bounds read and write in ANGLE | 9.6 | 0.0063 | None reported |
| Urgent | CVE-2026-78904 | Chromium: CVE-2026-78904 Type confusion in ANGLE | 9.6 | 0.0062 | None reported |
| Urgent | CVE-2026-17687 | Chromium: CVE-2026-17687 Type Confusion in ANGLE | 9.6 | 0.0056 | None reported |
| Urgent | CVE-2026-17655 | Chromium: CVE-2026-17655 Insufficient validation of untrusted input in ANGLE | 9.6 | 0.0055 | None reported |
| Urgent | CVE-2026-17697 | Chromium: CVE-2026-17697 Type Confusion in ANGLE | 9.6 | 0.0055 | None reported |
| Urgent | CVE-2025-26416 | webkit2gtk: In initializeSwizzler of SkBmpStandardCodec.cpp, there is a possible out of bounds write due to a heap buffer overflow | 9.8 | 0.0054 | None reported |
| Urgent | CVE-2026-17671 | Chromium: CVE-2026-17671 Insufficient validation of untrusted input in ANGLE | 9.6 | 0.0051 | None reported |
| Urgent | CVE-2026-17682 | Chromium: CVE-2026-17682 Integer overflow in ANGLE | 9.6 | 0.0051 | None reported |
| Urgent | CVE-2026-17704 | Chromium: CVE-2026-17704 Use after free in ANGLE | 9.6 | 0.0051 | None reported |
| Urgent | CVE-2026-17717 | Chromium: CVE-2026-17717 Integer overflow in ANGLE | 9.6 | 0.0051 | None reported |
| Urgent | CVE-2026-79131 | Chromium: CVE-2026-79131 Out of bounds write in ANGLE | 9.6 | 0.0048 | None reported |
| Urgent | CVE-2026-79149 | Chromium: CVE-2026-79149 Use after free in ANGLE | 9.6 | 0.0048 | None reported |
| Urgent | CVE-2026-79188 | Chromium: CVE-2026-79188 Out of bounds write in ANGLE | 9.6 | 0.0048 | None reported |
| Urgent | CVE-2026-79275 | Chromium: CVE-2026-79275 Use after free in ANGLE | 9.6 | 0.0048 | None reported |
| Urgent | CVE-2026-79043 | Chromium: CVE-2026-79043 Out of bounds write in ANGLE | 9.6 | 0.0046 | None reported |
| Urgent | CVE-2026-17718 | Chromium: CVE-2026-17718 Use after free in ANGLE | 9.6 | 0.0044 | None reported |
| Urgent | CVE-2026-17721 | Chromium: CVE-2026-17721 Out of bounds write in ANGLE | 9.6 | 0.0044 | None reported |
| Urgent | CVE-2026-17675 | Chromium: CVE-2026-17675 Out of bounds write in ANGLE | 9.6 | 0.0043 | None reported |
| Urgent | CVE-2026-17801 | Chromium: CVE-2026-17801 Out of bounds memory access in ANGLE | 9.6 | 0.0043 | None reported |
| Urgent | CVE-2026-13780 | Chromium: CVE-2026-13780 Insufficient validation of untrusted input in ANGLE | 9.6 | 0.0043 | None reported |
| Urgent | CVE-2026-13781 | Chromium: CVE-2026-13781 Insufficient validation of untrusted input in Skia | 9.6 | 0.0043 | None reported |
Showing 1 to 25 of 243
1Next
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.