CVE-2026-34982 | Vim modeline bypass via various options affects Vim < 9.2.0276

Vim is an open source, command line text editor. Prior to version 9.2.0276, a modeline sandbox bypass in Vim allows arbitrary OS command execution when a user opens a crafted file. The `complete`, `guitabtooltip` and `printheader` options are missing the `P_MLE` flag, allowing a modeline to be executed. Additionally, the `mapset()` function lacks a `check_secure()` call, allowing it to be abused from sandboxed expressions. Commit 9.2.0276 fixes the issue.

Published: 2026-04-06 Last update: 2026-04-22 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-34982 is rated Low Risk (34.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-34982

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-07 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-34982

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.2 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.8 [email protected]

Weakness enumeration for CVE-2026-34982

OS Trackers for CVE-2026-34982

vendor priority summary link
alpine — CVE-2026-34982: 1 source package rows (vim); 2 state rows across 2 repos (3.23-main, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2026-34982
debian not yet assigned CVE-2026-34982 not yet assigned priority: Debian including 1 source packages (vim), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-34982
redhat high — https://access.redhat.com/security/cve/CVE-2026-34982
suse high CVE-2026-34982 severity important: SUSE including 38 source package names (13.2-9.95:vim-9.2.0280-slfo.1.1_1.1, 13.2-9.95:vim-data-common-9.2.0280-slfo.1.1_1.1, …), 135 product×package rows across 40 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/toolbox, … (40 product lines)): Fixed 87, First Fixed 48. https://www.suse.com/security/cve/CVE-2026-34982/
ubuntu medium CVE-2026-34982 medium priority: Ubuntu including 1 source packages (vim), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): not-affected 4, released 4. https://ubuntu.com/security/CVE-2026-34982

Affected software / configurations for CVE-2026-34982

Vendor Product Version Raw CPE
vim vim < 9.2.0276 cpe:2.3:a:vim:vim:*:*:*:*:*:*:*:*

References for CVE-2026-34982

cvelogic Threat Intelligence