PatchSiren cyber security CVE debrief
CVE-2026-73076 vim CVE debrief
CVE-2026-73076 is a high-severity vulnerability in Vim, a command-line text editor. The vulnerability exists in the vimball.vim file, which allows a crafted vimball member to overwrite the installation record with attacker-chosen commands. These commands can execute with the privileges of the user running Vim when vimball#RmVimball() processes the matching record entry.
- Vendor
- vim
- Product
- Unknown
- CVSS
- HIGH 8.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-11
- Original CVE updated
- 2026-09-09
- Advisory published
- 2026-08-11
- Advisory updated
- 2026-09-09
Who should care
Defenders responsible for managing Vim installations, especially in multi-user environments or where Vim is used with elevated privileges, should assess exposure and prioritize patching or mitigation.
Why it matters
CVE-2026-73076 is a high-severity vulnerability in Vim that allows crafted vimball members to execute commands with user privileges. Defenders should prioritize patching or mitigating this vulnerability, especially in environments where Vim is used by multiple users or with elevated privileges. The vulnerability requires verification of affected versions and exploitation, but patching to version 9.2.0847 or later is recommended.
- Potential command execution with user privileges
- Possible elevation of privileges in multi-user environments
- Risk of malicious activity through crafted vimball members
Technical summary
The vulnerability exists in the vimball.vim file, which allows a crafted vimball member named .VimballRecord to overwrite the installation record with attacker-chosen commands. These commands can execute with the privileges of the user running Vim when vimball#RmVimball() processes the matching record entry. The issue is fixed in Vim version 9.2.0847. This high-severity vulnerability requires immediate attention, especially in multi-user environments or where Vim is used with elevated privileges. Affected product deployments should be identified, and defenders should prioritize patching or mitigating this vulnerability. Verification of affected versions and exploitation is necessary, but patching to version 9.2
Defensive priority
Defenders should prioritize patching or mitigating this vulnerability, especially in environments where Vim is used by multiple users or with elevated privileges.
Recommended defensive actions
- Patch Vim to version 9.2.0847 or later
- Restrict access to Vim installations where possible
- Monitor Vim usage for suspicious activity
- Verify affected Vim versions in your environment
- Review system logs for potential exploitation attempts
- Implement additional security measures for multi-user environments
- Track and prioritize patching for high-severity vulnerabilities
Evidence notes
The CVE record and NVD entry provide details about the vulnerability, including its CVSS score and weaknesses (CWE-94 and CWE-829). However, the corpus does not provide information on known exploitation or affected versions beyond Vim 9.2.0847 being patched.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-73076 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-73076
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-73076 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73076
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/vim/vim/commit/581a2f3ac9c6f96a26324f6b2c8c11415fd0d452
-
Source reference
Unverified legacy reference
URL: https://github.com/vim/vim/security/advisories/GHSA-r22p-fhw4-84p2
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.