# CVE-2026-73075: Vim: Out-of-bounds Access in Popup Opacity Handling

> An out-of-bounds access in Vim's popup opacity handling allows attackers to potentially execute code or cause a crash via crafted text properties.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** ALPINE-CVE-2026-73075, AZL-95973, BELL-CVE-2026-73075, DEBIAN-CVE-2026-73075, GHSA-pmvp-6rcj-98p4, MINI-vcg8-7hfw-6c6c

## What is CVE-2026-73075?

CVE-2026-73075 is a medium-severity memory corruption vulnerability in Vim Vim, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vim is an open source, command line text editor. From 9.2.0469 until 9.2.0843, popup_mark_opacity_zindex() in src/popupwin.c can use a negative w_winrow for a text-property-anchored popup with clipwindow and opacity, indexing before the screen array instead of accounting for w_popup_topoff and causing an out-of-bounds read and conditional write. This issue is fixed in version 9.2.0843.

Weakness: CWE-125 (Out-of-bounds Read), CWE-124 (Buffer Underwrite)

## Which versions are affected by CVE-2026-73075?

It affects 1 product.


Products: Vim Vim.

## How do I fix CVE-2026-73075?

Upgrade to a fixed version.

## Is CVE-2026-73075 being exploited?

There is no known exploitation of CVE-2026-73075 in the wild and no public exploit code.

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3075](https://insights.sbomify.com/CVE-2008-3075/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73075 and fix it if it is affected.

What it is: CVE-2026-73075 is a medium-severity memory corruption vulnerability in Vim Vim, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-73075 in the wild and no public exploit code.

Affected product: Vim Vim. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73075/ (Markdown: https://insights.sbomify.com/CVE-2026-73075/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73075
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73075
- OSV: https://osv.dev/vulnerability/CVE-2026-73075

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73075/
Summaries are generated and may contain mistakes; the official description above is the record.