CVE-2026-34714: Vim before 9.2.0272 allows code execution that happens immediately upon opening a crafted file in the default

This month

CRITICAL 9.2UPGRADE

CVE-2026-34714 is a critical-severity flaw (CVSS 9.2) affecting vim. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.2 (Critical)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-78, CWE-917
Published	2026-03-30
Last modified	2026-09-01

Publisher (CNA): MITRE · Vendor: vim

Last updated 2026-09-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-30 19:16 UTCPublished CVE record published
2026-09-01 13:18 UTCUpdated Record last modified

vim vim UPGRADE

Affected: >= 9.1.1390 and < 9.2.0272

Fixed in: 9.2.0272

Safe to downgrade to: a release before 9.1.1390

1. Check installed version

apt-cache policy vim || rpm -q vim || vim --version

2. UPGRADE to 9.2.0272 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade vim

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade vim

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 9.1.1390 (Debian / Ubuntu)

apt-cache madison vim sudo apt install vim=<VERSION_BEFORE_9.1.1390> sudo apt-mark hold vim

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vim sudo dnf downgrade vim-<VERSION_BEFORE_9.1.1390> sudo dnf versionlock add vim

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-34714?

vim: upgrade to 9.2.0272. Exact commands for each OS are on this page.

Is CVE-2026-34714 being exploited?

CVE-2026-34714 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-34714 affect?

CVE-2026-34714 affects vim. Severity is critical (CVSS 9.2). 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.

How urgent is CVE-2026-34714?

Priority 44/100. Critical severity

Software pages

Vim vulnerabilities

Related CVEs

CVE-2026-51400 HIGH 8.4 UPGRADE An issue in Vim Project v9.2.0389 and earlier allows a local attacker to execute arbitrary code via the vms_fi
CVE-2026-51401 HIGH 7.7 UPGRADE An issue in Vim Project v9.2.0389 and earlier allows a local attacker to execute arbitrary code via the vms_fi
CVE-2026-34982 HIGH 8.2 UPGRADE Vim is an open source, command line text editor
CVE-2026-73071 LOW 3.3 UPGRADE Vim is an open source, command line text editor
CVE-2026-73072 HIGH 7.3 UPGRADE Vim is an open source, command line text editor

References

← Back to latest CVEs