CVE-2026-34714: Vim command injection (CVSS 9.2)

Description

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.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityLow

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

Affected products

Vim≥ 9.1.1390 < 9.2.0272

Remediation

Fixed in

Vim≥ 9.2.0272

Patch & vendor advisories

References

https://access.redhat.com/security/cve/CVE-2026-34714
https://bugzilla.redhat.com/show_bug.cgi?id=2453139
https://github.com/vim/vim/commit/664701eb7576edb7c7c7d9f2d600815ec1f43459Patch
https://github.com/vim/vim/releases/tag/v9.2.0272Release Notes
https://github.com/vim/vim/security/advisories/GHSA-2gmj-rpqf-pxvhVendor Advisory
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34714.json
https://www.openwall.com/lists/oss-security/2026/03/30/3Mailing ListThird Party Advisory
http://www.openwall.com/lists/oss-security/2026/04/02/4Issue TrackingMailing List
http://www.openwall.com/lists/oss-security/2026/04/02/5Mailing List
http://www.openwall.com/lists/oss-security/2026/04/03/6Mailing List

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-34714 being actively exploited?

CVE-2026-34714 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.29%.

How severe is CVE-2026-34714?

CVE-2026-34714 has a CVSS 3.1 base score of 9.2, rated critical. EPSS estimates a 0.29% probability of exploitation.

Which products are affected by CVE-2026-34714?

Affected products include Vim.

How do I fix CVE-2026-34714?

Upgrade affected software to a fixed version, for example Vim 9.2.0272 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-34714 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo