Cyber Resilience

CVE-2026-46483

Command Injection in Vim ≤ 9.2.0479

Published
15 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 3.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS Score 0.0055 44th percentile
Risk Priority 32 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-46483 is a low-severity OS Command Injection (CWE-78) vulnerability in Vim Vim. Its CVSS base score is 3.6 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

{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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33412Same product: Vim Vim
CVE-2026-34982Same product: Vim Vim
CVE-2026-42307Same product: Vim Vim
CVE-2026-41411Same product: Vim Vim
CVE-2026-44656Same product: Vim Vim
CVE-2026-34714Same product: Vim Vim
CVE-2026-28417Same product: Vim Vim
CVE-2026-55895Same product: Vim Vim
CVE-2026-57453Same product: Vim Vim
CVE-2026-47167Same product: Vim Vim

Affected Assets

vim
vim
≤ 9.2.0479

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5
  • V1.2.8
  • V15.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect command sanitization during development.

Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.

Least privilege reduces the permissions available to any process that could be subverted by injected commands.

Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.

Secure engineering principles require proper neutralization of untrusted input before command construction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.

PR.PS-02 partial match
prevents

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

prevents

Secure development lifecycle mandates input validation and command construction practices that directly prevent argument injection.

prevents

Application security requirements include explicit rules for safe command-line argument handling and escaping.

prevents

Secure architecture principles discourage unsafe command invocation patterns and favor safer APIs.

prevents

Secure coding standards explicitly require proper neutralization of command arguments, directly eliminating CWE-88.

References