CVE-2026-52860

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

June 11, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Jun 11, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available

Arbitrary Code Execution via Python Omni-Completion in Vim < 9.2.0597 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-65p9-mwwx-7468
github Patch Available🟡 PoC Available

Arbitrary Code Execution via Python Omni-Completion in Vim < 9.2.0561 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-52mc-rq6p-rc7c
github_commit

commit c8c63673bc42 (vim/vim)

Fix landed in vim/vim commit c8c63673bc42 — awaiting tagged release

https://github.com/vim/vim/commit/c8c63673bc4253212820626aeeb75999d9a539d2

Vendor Advisories for CVE-2026-52860(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.0967-1ubuntu6.7) @ questing2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim9.2.0602-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0524-1 (17 versions)2:9.2.0782-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 90× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 243 total refreshes for this CVE.

  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 12:19 UTCEG score recompute
  3. 2026-09-01 12:19 UTCVendor advisory
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 23:50 UTCEG score recompute
  6. 2026-08-30 23:50 UTCVendor advisory
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 00:50 UTCEG score recompute
  14. 2026-08-25 00:50 UTCVendor advisory
  15. 2026-08-24 13:29 UTCVendor advisory
  16. 2026-08-24 12:20 UTCEG score recompute
  17. 2026-08-24 12:20 UTCVendor advisory
  18. 2026-08-23 22:30 UTCVendor advisory
  19. 2026-08-23 10:40 UTCEG score recompute
  20. 2026-08-23 10:40 UTCVendor advisory
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 19:15 UTCVendor advisory
  24. 2026-08-21 07:49 UTCEG score recompute
  25. 2026-08-21 07:49 UTCVendor advisory
Show 75 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:28 UTCVendor advisory
  3. 2026-08-20 08:50 UTCEG score recompute
  4. 2026-08-20 08:50 UTCVendor advisory
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 14:17 UTCEG score recompute
  7. 2026-08-19 14:17 UTCVendor advisory
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 10:24 UTCVendor advisory
  11. 2026-08-16 23:03 UTCEG score recompute
  12. 2026-08-16 23:03 UTCVendor advisory
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 11:05 UTCEG score recompute
  15. 2026-08-16 11:05 UTCVendor advisory
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 23:44 UTCVendor advisory
  18. 2026-08-15 10:39 UTCEG score recompute
  19. 2026-08-15 10:39 UTCVendor advisory
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 20:56 UTCVendor advisory
  22. 2026-08-14 09:35 UTCVendor advisory
  23. 2026-08-13 22:14 UTCEG score recompute
  24. 2026-08-13 22:14 UTCVendor advisory
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-13 09:40 UTCVendor advisory
  27. 2026-08-12 22:19 UTCEG score recompute
  28. 2026-08-12 22:19 UTCVendor advisory
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-12 10:58 UTCVendor advisory
  31. 2026-08-11 23:36 UTCEG score recompute
  32. 2026-08-11 23:36 UTCVendor advisory
  33. 2026-08-11 12:15 UTCVendor advisory
  34. 2026-08-11 00:54 UTCEG score recompute
  35. 2026-08-11 00:54 UTCVendor advisory
  36. 2026-08-11 00:00 UTCEPSS rescore
  37. 2026-08-10 13:33 UTCVendor advisory
  38. 2026-08-10 02:09 UTCVendor advisory
  39. 2026-08-09 14:48 UTCEG score recompute
  40. 2026-08-09 14:48 UTCVendor advisory
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-09 03:27 UTCEG score recompute
  43. 2026-08-09 03:27 UTCVendor advisory
  44. 2026-08-08 16:37 UTCEPSS rescore
  45. 2026-08-08 16:06 UTCVendor advisory
  46. 2026-08-08 04:45 UTCVendor advisory
  47. 2026-08-07 17:22 UTCEG score recompute
  48. 2026-08-07 17:22 UTCVendor advisory
  49. 2026-08-07 06:01 UTCVendor advisory
  50. 2026-08-06 18:40 UTCEG score recompute
  51. 2026-08-06 18:40 UTCVendor advisory
  52. 2026-08-06 13:47 UTCEPSS rescore
  53. 2026-08-06 07:19 UTCVendor advisory
  54. 2026-08-05 19:58 UTCEG score recompute
  55. 2026-08-05 19:58 UTCVendor advisory
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-04 15:49 UTCEG score recompute
  58. 2026-08-04 15:49 UTCVendor advisory
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:39 UTCEPSS rescore
  61. 2026-08-03 21:30 UTCEG score recompute
  62. 2026-08-03 21:30 UTCVendor advisory
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 10:09 UTCVendor advisory
  65. 2026-08-02 19:34 UTCVendor advisory
  66. 2026-08-02 08:13 UTCEG score recompute
  67. 2026-08-02 08:13 UTCVendor advisory
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 20:51 UTCVendor advisory
  70. 2026-08-01 09:30 UTCEG score recompute
  71. 2026-08-01 09:30 UTCVendor advisory
  72. 2026-08-01 04:16 UTCEPSS rescore
  73. 2026-07-31 13:35 UTCVendor advisory
  74. 2026-07-31 00:37 UTCEG score recompute
  75. 2026-07-31 00:37 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-52860?
CVE-2026-52860 is a high vulnerability published on June 11, 2026. 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…
When was CVE-2026-52860 disclosed?
CVE-2026-52860 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52860 actively exploited?
CVE-2026-52860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.2% of all scored CVEs.
What is the CVSS score of CVE-2026-52860?
CVE-2026-52860 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52860, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52860

Explore →

Is Your Infrastructure Affected by CVE-2026-52860?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.