CVE-2026-73076
Local command execution via crafted vimball in Vim before 9.2.0847
Is CVE-2026-73076 being exploited?
Not confirmed. CVE-2026-73076 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-73076?
CVE-2026-73076 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-73076?
Yes. A fix has been recorded for CVE-2026-73076. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-73076 affect?
CVE-2026-73076 affects Vim < 9.2.0847, runtime/autoload/vimball.vim, vimball#RmVimball. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-73076?
Upgrade to Vim 9.2.0847+ and avoid opening untrusted vimball files
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary OS/Ex commands execute as the user when a crafted .VimballRecord is processed, enabling local code execution.
Patch when possible
- affected< 9.2.0847
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.