PatchSiren cyber security CVE debrief
CVE-2026-73075 vim CVE debrief
A vulnerability in Vim, a command-line text editor, allows for an out-of-bounds read and conditional write due to improper handling of a negative w_winrow value in the popup_mark_opacity_zindex() function. This issue affects Vim versions from 9.2.0469 to 9.2.0842 and is fixed in version 9.2.0843. The vulnerability can be exploited by an attacker to potentially execute arbitrary code or cause a denial of service. Defenders should verify their Vim version and apply the patch to prevent potential exploitation.
- Vendor
- vim
- Product
- Unknown
- CVSS
- MEDIUM 4.6
- 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 maintaining and securing systems that use Vim should verify their version and apply the patch to prevent potential exploitation. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance.
Why it matters
A vulnerability in Vim, a command-line text editor, allows for an out-of-bounds read and conditional write due to improper handling of a negative w_winrow value in the popup_mark_opacity_zindex() function. This issue affects Vim versions from 9.2.0469 to 9.2.0842 and is fixed in version 9.2.0843.
- Verify Vim version and apply patch to prevent potential exploitation
- Monitor for potential exploitation
- Update to version 9.2.0843 or later
Technical summary
The vulnerability is caused by an out-of-bounds read and conditional write in the popup_mark_opacity_zindex() function in Vim versions from 9.2.0469 to 9.2.0842. The issue is fixed in version 9.2.0843. The vulnerability can be exploited by an attacker to potentially execute arbitrary code or cause a denial of service. Defenders should prioritize verifying their Vim version and applying the patch to prevent potential exploitation. The CVE record and NVD detail page provide additional information on the vulnerability.
Defensive priority
Defenders should prioritize verifying their Vim version and applying the patch to prevent potential exploitation.
Recommended defensive actions
- Verify Vim version and apply patch
- Monitor for potential exploitation
- Update to version 9.2.0843 or later
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The vulnerability is caused by an out-of-bounds read and conditional write in the popup_mark_opacity_zindex() function. The issue is fixed in version 9.2.0843. Evidence is limited to the supplied CVE record and NVD detail page. Defenders should verify their Vim version and review the official advisory for affected scope and severity. The CVE record was published on 2026-08-11T16:17:38.840Z and has not been modified since then.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-73075 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-73075
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-73075 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73075
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/security/advisories/GHSA-pmvp-6rcj-98p4
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.