# CVE-2025-22134: heap-buffer-overflow with visual mode in Vim < 9.1.1003

> A heap-buffer overflow in Vim allows attackers to cause crashes or potentially execute code when visual mode is active during buffer switching.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Jan 2025
- **Updated:** 14 Mar 2025
- **Also known as:** ALPINE-CVE-2025-22134, AZL-55500, AZL-55582, BELL-CVE-2025-22134, CLSA-2025-1765286037, DEBIAN-CVE-2025-22134, ECHO-392a-f4a0-dbde, GHSA-5rgf-26wj-48v8, MGASA-2025-0014, OESA-2025-1166, UBUNTU-CVE-2025-22134, USN-7220-1

## What is CVE-2025-22134?

CVE-2025-22134 is a medium-severity memory corruption vulnerability in Netapp Bootstrap Os, published on 13 Jan 2025. 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

When switching to other buffers using the :all command and visual mode still being active, this may cause a heap-buffer overflow, because Vim does not properly end visual mode and therefore may try to access beyond the end of a line in a buffer. In Patch 9.1.1003 Vim will correctly reset the visual mode before opening other windows and buffers and therefore fix this bug. In addition it does verify that it won't try to access a position if the position is greater than the corresponding buffer line. Impact is medium since the user must have switched on visual mode when executing the :all ex command. The Vim project would like to thank github user gandalf4a for reporting this issue. The issue has been fixed as of Vim patch v9.1.1003

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-22134?

It affects 3 products.


Products: Neovim Neovim, Netapp Bootstrap Os, Vim Vim.

## How do I fix CVE-2025-22134?

Apply the vendor's patch.

## Is CVE-2025-22134 being exploited?

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

## Other vulnerabilities in Netapp Bootstrap Os

- [CVE-2019-12735](https://insights.sbomify.com/CVE-2019-12735/): Command injection in n/a (high 8.6)
- [CVE-2022-3591](https://insights.sbomify.com/CVE-2022-3591/): Use After Free in vim/vim (high 7.8)
- [CVE-2026-45130](https://insights.sbomify.com/CVE-2026-45130/): Vim: Heap Buffer Overflow in spell file loading (medium 6.6)
- [CVE-2026-25749](https://insights.sbomify.com/CVE-2026-25749/): Heap Overflow in Vim (medium 6.6)
- [CVE-2024-43374](https://insights.sbomify.com/CVE-2024-43374/): Vim heap-use-after-free in src/arglist.c:207 (medium 4.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22134 and fix it if it is affected.

What it is: CVE-2025-22134 is a medium-severity memory corruption vulnerability in Netapp Bootstrap Os, published on 13 Jan 2025. 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-2025-22134 in the wild and no public exploit code.

Affected product: Netapp Bootstrap Os. 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-2025-22134/ (Markdown: https://insights.sbomify.com/CVE-2025-22134/index.md)
```

## Sources

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

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