LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 9.2Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A malicious file can cause vulnerable Vim versions to run code as soon as the file is opened, including with default settings. Successful exploitation could expose sensitive data, alter files, or disrupt the workstation under the user’s permissions. The source bundle identifies Vim versions before 9.2.0272 as vulnerable.

Executive priority

Treat as an urgent workstation and engineering-environment remediation. Prioritize privileged administrators, developers, production operators, and build systems because successful code execution inherits the user’s access. Confirm vendor-fixed packages promptly; current evidence does not show active exploitation.

Technical view

Vim before 9.2.0272 improperly processes a crafted %{expr} expression in tabpanel because the relevant option lacks P_MLE protection. This permits expression injection leading to code execution. The supplied CVSS 3.1 score is 9.2, with high confidentiality and integrity impact and changed scope.

Likely exposure

Developer workstations, administrative systems, build environments, and servers are exposed where Vim before 9.2.0272 may open attacker-controlled or untrusted files. Actual exposure depends on installed package versions and whether downstream distributions backported the fix.

Exploitation context

The flaw requires a crafted file to reach and be opened by vulnerable Vim. The bundle states execution occurs immediately in the default configuration. CVE is not listed as KEV in the supplied data, and the sources provided do not establish active exploitation.

Researcher notes

The reported weakness combines command and expression injection classifications, CWE-78 and CWE-917. Scope assessment should distinguish upstream versions from distribution packages carrying backports. The bundle’s affected-product metadata is sparse and internally awkward, so use the explicit “before 9.2.0272” statement and vendor advisory when validating exposure.

Mitigation direction

  • Upgrade Vim to 9.2.0272 or a later vendor-supported fixed build.
  • Check distribution advisories for backported fixes before judging package versions.
  • Restrict opening untrusted files with vulnerable Vim until remediation is complete.
  • Prioritize systems where Vim users hold administrative or sensitive-data access.

Validation and detection

  • Inventory Vim versions across workstations, servers, containers, and build environments.
  • Confirm installed builds include release 9.2.0272 or commit 664701eb7576.
  • Review distribution security notices for fixed package revisions or backports.
  • Identify workflows where users receive or open files from untrusted sources.
  • After updating, verify the effective Vim binary and package version.
Prepared
Confidence
high
Sources
6

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.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-917: Exact CWE lookup

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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-34714 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
9.2CVSS 3.1CriticalCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L2.56mitre
8.6CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H1.86redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.2Critical
CVSS 3.1 vector shape for CVE-2026-34714Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
redhat-SADPvim: Vim: Arbitrary code execution via crafted file
other:Red Hat severity ratingcvssV3_1
  • 2026-03-30T19:01:54.837Z: Reported to Red Hat.
  • 2026-03-30T18:27:55.752Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
VimVim0unaffected
Weakness

CWE details

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.

CWE-917 · source CWE mapping

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.