Linux ·
openSUSE Leap · Security advisory · August 28, 2026
openSUSE Leap · Security advisory · August 28, 2026OPENSUSE-SU-2026:21671-1: vim security update
OPENSUSE-SU-2026:21671-1, released August 28, 2026, fixes 8 CVEs in vim (version 9.2.0957-160000.1.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
8.8
Base score, 0 to 10
Highest EPSS
0.0031
24th percentile
Priority of the 8 CVEs
Patch now 0
Urgent 0
High 4
Routine 4
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| vim | opensuse-leap 16.0 | 9.2.0957-160000.1.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-73078 | Vim: Arbitrary Code Execution via Netrw Menu Construction | 8.8 | 0.0031 | None reported |
| High | CVE-2026-73077 | Vim: Arbitrary Code Execution via Shell Keyword Lookup | 8.8 | 0.0014 | None reported |
| High | CVE-2026-73076 | Vim: Arbitrary Command Execution via Malicious `.VimballRecord` Entry Replay in `vimball.vim` | 8.8 | 0.0013 | None reported |
| High | CVE-2026-73072 | Vim: Heap Buffer Overflow when Loading a Spell File | 8.8 | 0.0012 | None reported |
| Routine | CVE-2026-73070 | Vim: Stack Buffer Overflow in the Vim Socket Server | 5.5 | 0.0019 | None reported |
| Routine | CVE-2026-73071 | Vim: Use-after-free in JSON Decoding | 3.3 | 0.0011 | None reported |
| Routine | CVE-2026-73074 | Vim: Heap Buffer Overflow in Text Property Handling | 6.7 | 0.0010 | None reported |
| Routine | CVE-2026-73075 | Vim: Out-of-bounds Access in Popup Opacity Handling | 3.9 | 0.0009 | None reported |
Showing 1 to 8 of 8
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.