Command Injection in Vim (CVE-2026-57453)
Summary
Command injection in Vim (CVE-2026-57453). Confidential information can be exposed externally. Mitigation: upgrade to 9.2.0678 or later.
Original description
The description as published by the source.
Vim is an open source, command line text editor. From 9.1.1784 until 9.2.0678, when the bundled zip plugin autoload/zip.vim falls back to PowerShell to browse, read, extract, update or delete entries in a zip archive, it builds the PowerShell command by inserting archive entry names that are quoted only for the shell, not for PowerShell. A crafted entry name can break out of the intended string context and cause PowerShell to execute arbitrary commands with the privileges of the user running Vim, triggered by opening, viewing or extracting the archive. This vulnerability is fixed in 9.2.0678.
Source: NIST National Vulnerability Database NVD
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 CVE-2026-57453 has been found in Vim.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade Vim to 9.2.0678 or later.
If unsure, ask your IT team or search "Vim CVE-2026-57453" on the vendor's site.
CVE-2026-57453 (Vim) — CWE-77 / CVSS v3 6.5
Attack vector: local / unauthenticated
Patched: 9.2.0678 — 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.
A vulnerability (CWE-77) exists in Vim.
Check the vendor advisory for the affected versions of Vim.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 9.2.0678.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'Vim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Vimを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Vim to 9.2.0678ステージング環境で 9.2.0678 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-57453 vim Fixed in: 9.2.0854-r0
- BellSoft Alpaquita BELL-CVE-2026-57453 vim Fixed in: 9.2.0747-r0
- Debian DEBIAN-CVE-2026-57453 vim Fixed in: 2:9.2.0782-1
- Ubuntu UBUNTU-CVE-2026-57453 vim Fixed in: 2:9.1.2141-1ubuntu4.6