Vulnerability in vim (UBUNTU-CVE-2026-59858)

Summary

Vulnerability in vim (UBUNTU-CVE-2026-59858). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2:7.4.052-1ubuntu3.1+esm31 or later.

Original description

The description as published by the source.

Vim is an open source, command line text editor. Prior to 9.2.0735, the C omni-completion script in runtime/autoload/ccomplete.vim interpolates the typeref: or typename: extension field of a tags entry, without escaping, into a :vimgrep pattern that is run through :execute. Because :vimgrep honors the bar as a command separator, a crafted tag field can close the search pattern and append an arbitrary Ex command; opening a hostile .c file whose project tags file contains such an entry and invoking C omni-completion runs that command as the editing user. This issue is fixed in version 9.2.0735.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-59858 has been found in vim.
Successful exploitation can lead to full system takeover.
What to do: upgrade vim to 2:7.4.052-1ubuntu3.1+esm31 or later.
If unsure, ask your IT team or search "vim UBUNTU-CVE-2026-59858" on the vendor's site.

UBUNTU-CVE-2026-59858 (vim)
Attack vector: local / unauthenticated
Patched: 2:7.4.052-1ubuntu3.1+esm31 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in vim.

📍 Affected scope

Check the vendor advisory for the affected versions of vim.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2:7.4.052-1ubuntu3.1+esm31.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vim' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'vim' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で vim を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade vim to 2:7.4.052-1ubuntu3.1+esm31
```
ステージング環境で 2:7.4.052-1ubuntu3.1+esm31 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:7.4.052-1ubuntu3.1+esm31"}]}]

Ubuntu:Pro:16.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:7.4.1689-3ubuntu1.5+esm37"}]}]

Ubuntu:Pro:18.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:8.0.1453-1ubuntu1.13+esm22"}]}]

Ubuntu:Pro:20.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:8.1.2269-1ubuntu5.32+esm10"}]}]

Ubuntu:22.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:8.2.3995-1ubuntu2.34"}]}]

Ubuntu:24.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:9.1.0016-1ubuntu7.18"}]}]

Ubuntu:26.04:LTS vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:9.1.2141-1ubuntu4.7"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report github.com
report github.com