# CVE-2026-57451: Vim: Out-of-bounds Read in Text Property Count

> An attacker can cause a crash in Vim by providing a crafted undo file that triggers an out-of-bounds read due to unchecked property counts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **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:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** ALPINE-CVE-2026-57451, AZL-91116, BELL-CVE-2026-57451, DEBIAN-CVE-2026-57451, ECHO-f07e-8df7-39f4, GHSA-f36c-2qcp-7gpw, MINI-vvg5-xfr4-6688

## What is CVE-2026-57451?

CVE-2026-57451 is a medium-severity memory corruption vulnerability in Vim Vim, published on 25 Jun 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.0670, get_text_props() in src/textprop.c reads a uint16 property count stored inline after a line's text and returns it as the number of 32-byte textprop_T entries that follow. The only check is a floor that guarantees room for a single entry; the count is never checked against the amount of data actually present. A line that declares a large count while carrying little data causes consumers to read far past the end of the line buffer. Such a line can be delivered through a crafted undo file, leading to a crash. This vulnerability is fixed in 9.2.0670.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Vim Vim.

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

Upgrade to a fixed version.

## Is CVE-2026-57451 being exploited?

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

What it is: CVE-2026-57451 is a medium-severity memory corruption vulnerability in Vim Vim, published on 25 Jun 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-57451 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-57451/ (Markdown: https://insights.sbomify.com/CVE-2026-57451/index.md)
```

## Sources

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

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