Cyber Resilience

CVE-2026-34714

Command Injection in Vim 9.1.1390 – 9.2.0272

Command Injection
Published
30 March 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
EPSS Score 0.0059 45th percentile
Risk Priority 65 floored blend · peak EPSS

Summary

CVE-2026-34714 is a critical-severity OS Command Injection (CWE-78) vulnerability in Vim Vim. Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 45th 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.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-34714 is a high-severity vulnerability (CVSS 3.1 score of 9.2) affecting Vim text editor versions prior to 9.2.0272. It enables arbitrary code execution upon opening a specially crafted file in the default configuration, stemming from a %{expr} injection flaw in the tabpanel feature due to the absence of P_MLE protection. This issue is classified under CWE-78 (OS Command Injection) and was publicly disclosed on March 30, 2026.

The vulnerability can be exploited by a local attacker with low complexity and no privileges required, as it requires no user interaction beyond convincing a victim to open the malicious file (AV:L/AC:L/PR:N/UI:N). Successful exploitation changes scope (S:C) and grants high-impact confidentiality and integrity violations alongside low availability impact (C:H/I:H/A:L), allowing immediate code execution on the victim's system in the context of the Vim process.

Mitigation is addressed in Vim's official patches, including commit 664701eb7576edb7c7c7d9f2d600815ec1f43459 and the release of version 9.2.0272. The GitHub security advisory (GHSA-2gmj-rpqf-pxvh) and oss-security mailing list announcements detail the fix, recommending users upgrade to Vim 9.2.0272 or later to prevent exploitation.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Vim before 9.2.0272 allows code execution that happens immediately upon opening a crafted file in the default configuration, because %{expr} injection occurs with tabpanel lacking P_MLE.

CWE(s)
CWE-78CWE-917

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.
attack.mitre.org →
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
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.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34982Same product: Vim Vim
CVE-2026-44656Same product: Vim Vim
CVE-2026-41411Same product: Vim Vim
CVE-2026-33412Same product: Vim Vim
CVE-2026-42307Same product: Vim Vim
CVE-2026-46483Same product: Vim Vim
CVE-2026-28417Same product: Vim Vim
CVE-2026-55895Same product: Vim Vim
CVE-2026-57453Same product: Vim Vim
CVE-2026-39881Same product: Vim Vim

Affected Assets

vim
vim
9.1.1390 — 9.2.0272

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
  • V1.1.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

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

SI-10 Information Input Validation good match

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

AC-6 Least Privilege partial match

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

CM-7 Least Functionality partial match

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

SA-8 Security and Privacy Engineering Principles partial match

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.

A.8.29 Security testing in development and acceptance mostly match
finds

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

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and output encoding that directly prevent expression-language injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including EL injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping and parameterization of expression-language statements.

References