# CVE-2026-73074: Vim: Heap Buffer Overflow in Text Property Handling

> An integer overflow in Vim's text property handling allows attackers to trigger a heap buffer overflow, potentially leading to code execution or crashes.

- **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/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:** 12 Aug 2026
- **Also known as:** ALPINE-CVE-2026-73074, AZL-95553, BELL-CVE-2026-73074, DEBIAN-CVE-2026-73074, ECHO-82d9-53fe-5993, GHSA-hm4g-pjfx-m27j, MINI-q786-5grw-2qqf, ROOT-OS-DEBIAN-11-CVE-2026-73074, ROOT-OS-DEBIAN-12-CVE-2026-73074, UBUNTU-CVE-2026-73074

## What is CVE-2026-73074?

CVE-2026-73074 is a high-severity 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. Prior to 9.2.0841, prop_add_one() in src/textprop.c uses the proplen value from get_text_props() to increment a uint16_t property count beyond 0xffff, wrapping the count to zero and copying existing text-property records into a heap allocation sized for none of them. This issue is fixed in version 9.2.0841.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Vim Vim.

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

Upgrade to a fixed version.

## Is CVE-2026-73074 being exploited?

There is no known exploitation of CVE-2026-73074 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-73074 and fix it if it is affected.

What it is: CVE-2026-73074 is a high-severity 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-73074 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-73074/ (Markdown: https://insights.sbomify.com/CVE-2026-73074/index.md)
```

## Sources

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

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