Skip to content
Noroxi
CVE-2026-52860· NVD / CVE Program· CNA GitHub_M

Vim: Arbitrary Code Execution via Python Omni-Completion

Vim is an open source, command line text editor. Prior to version 9.2.0597, Vim's Python omni-completion executes reconstructed function and class definitions from the current buffer with exec() as part of populating the completion dictionary. Python evaluates function default values, parameter annotations, and class base expressions at definition time, so a hostile buffer can execute attacker-controlled Python expressions during omni-completion. The existing g:pythoncomplete_allow_import mitigation (GHSA-52mc-rq6p-rc7c) does not cover this path, because the attacker-controlled code is not a harvested import/from statement. This issue has been patched in version 9.2.0597.

HighCVSS 7.5 · v4.0—No exploit Fix available
Published
Jun 11, 2026
Updated
Sep 17, 2026
EPSS
0.4% · 33th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.5
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
vimvim

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • vim vimbefore 9.2.0597

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • vim vim

    • < 9.2.0597affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.23vimbefore 9.2.0602-r09.2.0602-r0
Debian:12vimall versions—
Debian:14vimbefore 2:9.2.0782-12:9.2.0782-1
Red Hat:hummingbird:1vimbefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-commonbefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-databefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-default-editorbefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-enhancedbefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-filesystembefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-minimalbefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1vim-X11before 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1
Red Hat:hummingbird:1xxdbefore 0:9.2.967-1.1.hum10:9.2.967-1.1.hum1

Same product

vim: all records

Other highest-scoring records for the same primary product.

  • CVE-2008-2712Vim 7.1.314, 6.4, and other versions allows user-assisted remote attackers to execute arbitrary commands via Vim scripts that do not properl
    42Plan
  • CVE-2022-0318Heap-based Buffer Overflow in vim/vim
    40Plan
  • CVE-2019-12735getchar.c in Vim before 8.1.1365 and Neovim before 0.3.6 allows remote attackers to execute arbitrary OS commands via the :source! command i
    40Plan
  • CVE-2017-6350An integer overflow at an unserialize_uep memory allocation site would occur for vim before patch 8.0.0378, if it does not properly validate
    40Plan
  • CVE-2017-6349An integer overflow at a u_read_undo memory allocation site would occur for vim before patch 8.0.0377, if it does not properly validate valu
    40Plan
  • CVE-2017-5953vim before patch 8.0.0322 does not properly validate values for tree length when handling a spell file, which may result in an integer overf
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
vim vim9.2.0597 · descriptionVendor (CNA)
alpine:vim9.2.0602-r0 · Alpine:v3.23Package registry (OSV)
debian:vim2:9.2.0782-1 · Debian:14Package registry (OSV)
red hat:vim0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-common0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-data0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-default-editor0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-enhanced0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-filesystem0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-minimal0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:vim-X110:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:xxd0:9.2.967-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-5745614 days apartVim: Arbitrary Code Execution via Python Omni-Completion Docstrings
    33Monitor
  • CVE-2026-5985628 days apartVim: Arbitrary Code Execution via PHP Omni-Completion
    33Monitor
  • CVE-2026-5985828 days apartVim: Arbitrary Code Execution via C Omni-Completion
    33Monitor
  • CVE-2026-7307661 days apartVim: Arbitrary Command Execution via Malicious `.VimballRecord` Entry Replay in `vimball.vim`
    33Monitor
  • CVE-2026-3988164 days apartVim Ex command injection in Vims NetBeans integration
    31Monitor
  • CVE-2026-4396169 days apartVim: vimscript injection via unescaped filename in netrw s:netrwmarkfile() filter() expression allows arbitrary code execution
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
A
Scope
X

Weakness class (CWE)

CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records