CVE-2026-34714: Vim before 9.2.0272 allows code execution that happens immediately upon opening a crafted file in the defau...
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.
Security readout for executives and security teams
Plain-English summary
A crafted file can cause Vim to run code as soon as it is opened in the default configuration. For businesses, the practical risk is developer or administrator workstations processing untrusted files with vulnerable Vim versions before 9.2.0272.
Executive priority
Treat this as urgent for engineering and operations environments because Vim is widely present and the reported impact is code execution from a crafted file. Prioritize patching systems that handle external or untrusted files.
Technical view
The issue is described as %{expr} injection in Vim tabpanel handling where P_MLE was missing. The published CVSS 3.1 score is 9.2, with local attack vector, low complexity, no privileges, changed scope, and high confidentiality and integrity impact.
Likely exposure
Exposure is most likely on developer, operations, and server environments running Vim before 9.2.0272, especially where users open files from email, tickets, repositories, archives, or external partners. Distribution package status should be checked with the relevant vendor advisory.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The documented trigger is opening a crafted file, so phishing, shared repositories, support bundles, and downloaded archives are plausible delivery paths.
Researcher notes
Evidence supports a Vim-specific expression injection flaw fixed in 9.2.0272. The affected-version metadata in the bundle is sparse, so avoid overgeneralizing distro exposure. No public exploit status is established by the supplied sources.
Mitigation direction
Upgrade Vim to 9.2.0272 or a vendor-patched package.
Check Red Hat and other OS vendor advisories for backported fixes.
Restrict opening untrusted files in vulnerable Vim versions.
Prioritize developer and administrator endpoints for remediation.
Update golden images and CI environments that include Vim.
Validation and detection
Inventory Vim versions across workstations, servers, containers, and base images.
Confirm package builds include the fix for commit 664701e or release 9.2.0272.
Review vendor package status for supported operating systems.
Check endpoint controls for suspicious child processes spawned from Vim.
Validate remediation through standard package vulnerability scanning.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')
Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.