OS Command Injection in Vim (CVE-2026-46483)
Summary
OS command injection in Vim (CVE-2026-46483). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.2.0479 or later.
Original description
The description as published by the source.
Vim is an open source, command line text editor. Prior to 9.2.0479, a command injection vulnerability exists in tar#Vimuntar() in
runtime/autoload/tar.vim when decompressing .tgz archives on Unix-like systems. The function builds :!gunzip and :!gzip -d commands using shellescape(tartail) without the {special} flag, allowing a crafted archive filename to trigger Vim cmdline-special expansion and execute shell commands in the user's context. This vulnerability is fixed in 9.2.0479.
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-46483 has been found in Vim.
Risk of unauthorized operations or information disclosure. CVSS score: 3.6/10.
What to do: upgrade Vim to 9.2.0479 or later.
If unsure, ask your IT team or search "Vim CVE-2026-46483" on the vendor's site.
CVE-2026-46483 (Vim) — CWE-78 / CVSS v3 3.6
Attack vector: local / unauthenticated
Patched: 9.2.0479 — 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.
OS command injection (CWE-78) exists in Vim.
Check the vendor advisory for the affected versions of Vim.
Severity: Low (CVSS 3.6/10). Risk of unauthorized operations or information disclosure.
Update to 9.2.0479.
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.0479ステージング環境で 9.2.0479 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-46483 vim Fixed in: 9.2.0481-r0
- BellSoft Alpaquita BELL-CVE-2026-46483 vim Fixed in: 9.2.0481-r0
- Debian DEBIAN-CVE-2026-46483 vim
- Ubuntu UBUNTU-CVE-2026-46483 vim Fixed in: 2:7.4.052-1ubuntu3.1+esm28