# CVE-2026-44656: Vim: OS Command Injection via 'path' completion

> An attacker can execute arbitrary shell commands by crafting a file with malicious modelines that trigger command injection during Vim's :find completion.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/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:** 8 May 2026
- **Updated:** 11 May 2026
- **Also known as:** ALPINE-CVE-2026-44656, AZL-86249, BELL-CVE-2026-44656, CLSA-2026-1779806430, CLSA-2026-1779821440, DEBIAN-CVE-2026-44656, ECHO-dbb6-47a0-a981, GHSA-hwg5-3cxw-wvvg, UBUNTU-CVE-2026-44656

## What is CVE-2026-44656?

CVE-2026-44656 is a medium-severity command injection vulnerability in Vim Vim, published on 8 May 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 version 9.2.0435, an OS command injection vulnerability exists in Vim's :find command-line completion. When the path option contains backtick-enclosed shell commands, those commands are executed during file name completion. Because the path option lacks the P_SECURE flag, it can be set from a modeline, allowing an attacker who controls the contents of a file to execute arbitrary shell commands when the user opens that file in Vim and triggers :find completion. This issue has been patched in version 9.2.0435.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Vim Vim.

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

Upgrade to a fixed version.

## Is CVE-2026-44656 being exploited?

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

Public exploit code:

- This repository provides a reproduction environment for CVE-2026-44656. (github_poc): https://github.com/CryingN/CVE-2026-44656

## 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-44656 and fix it if it is affected.

What it is: CVE-2026-44656 is a medium-severity command injection vulnerability in Vim Vim, published on 8 May 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-44656 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-44656/ (Markdown: https://insights.sbomify.com/CVE-2026-44656/index.md)
```

## Sources

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

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