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.
Security readout for executives and security teams
Plain-English summary
A crafted text file can make vulnerable Vim versions run operating-system commands when a user opens it. This matters most where developers, administrators, or automation accounts open files from email, repositories, tickets, archives, or other untrusted sources.
Executive priority
Treat as high priority for developer and administrator environments. The vulnerability needs user interaction, but the potential outcome is command execution in a trusted user context, which can expose credentials, source code, and operational systems.
Technical view
Vim before 9.2.0276 has a modeline sandbox bypass. The complete, guitabtooltip, and printheader options lacked the P_MLE flag, and mapset() lacked check_secure(), allowing sandboxed expression abuse. The CVSS 3.1 score is 8.2 with local attack vector and required user interaction.
Likely exposure
Exposure is likely on developer workstations, admin jump hosts, servers, containers, and build images running Vim below 9.2.0276. Risk increases where users open third-party files, cloned repositories, support artifacts, or downloaded text files in Vim.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires a victim to open a crafted file in vulnerable Vim, but the reported impact is arbitrary OS command execution with high confidentiality and integrity impact.
Researcher notes
The key implementation issues are missing modeline restrictions on specific options and absent secure-context checking in mapset(). Evidence in the bundle identifies the upstream fix commit and release, but does not provide active exploitation confirmation.
Mitigation direction
Upgrade Vim to 9.2.0276 or a vendor-backported fixed package.
Apply relevant Red Hat security errata where Red Hat packages are in use.
Prioritize systems used by developers, administrators, and automation operators.
Avoid opening untrusted files in vulnerable Vim until patched.
Check vendor guidance for any interim controls or platform-specific fixes.
Validation and detection
Inventory Vim versions across endpoints, servers, containers, and base images.
Confirm installed packages include the 9.2.0276 fix or vendor backport.
Review Red Hat advisory applicability for affected Red Hat environments.
Identify workflows where users open external files in Vim.
Track remediation evidence in vulnerability management records.
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.
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
28Source 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.