# CVE-2026-59856: Vim: Arbitrary Code Execution via PHP Omni-Completion

> Attackers can execute arbitrary OS commands by tricking a victim into opening a crafted PHP file and triggering omni-completion in Vim.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/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:** 9 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** ALPINE-CVE-2026-59856, AZL-92160, BELL-CVE-2026-59856, DEBIAN-CVE-2026-59856, ECHO-ee84-f5bb-81bf, GHSA-fh26-8f79-wj97, MINI-3v96-95qr-j2vr, ROOT-OS-DEBIAN-11-CVE-2026-59856, ROOT-OS-DEBIAN-12-CVE-2026-59856, UBUNTU-CVE-2026-59856

## What is CVE-2026-59856?

CVE-2026-59856 is a high-severity code injection vulnerability in Vim Vim, published on 9 Jul 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.0736, the PHP omni-completion script in runtime/autoload/phpcomplete.vim interpolates a class or trait name, taken from the contents of the edited buffer, into a search() pattern that is run via win_execute() without escaping. A name containing a single quote can terminate the search() string argument early, and because the bar is honored as an Ex command separator, the remainder of the name is run as Ex commands; via the :! command this allows arbitrary operating-system command execution when a victim opens a crafted PHP file and invokes omni-completion. This issue is fixed in version 9.2.0736.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Vim Vim.

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

Upgrade to a fixed version.

## Is CVE-2026-59856 being exploited?

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

What it is: CVE-2026-59856 is a high-severity code injection vulnerability in Vim Vim, published on 9 Jul 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-59856 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-59856/ (Markdown: https://insights.sbomify.com/CVE-2026-59856/index.md)
```

## Sources

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

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