CVE-2026-52858

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 90% 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 — Patch released 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.0561, the Python omni-completion script in python3complete.vim for Vim with the +python3 interpreter enabled (and the legacy pythoncomplete.vim for builds with the +python interpreter) executes the import and from statements found in the current buffer through Python's import machinery. Because the buffer's working directory is on sys.path, opening a hostile .py file with a sibling Python package and invoking omni-completion runs that package's top-level code as the editing user. This issue has been patched in version 9.2.0561.

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
10%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 15, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
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 4b850457e12e (vim/vim)

Fix landed in vim/vim commit 4b850457e12e — awaiting tagged release

https://github.com/vim/vim/commit/4b850457e12e1a678dd209f2868154f7553cbf8d

Vendor Advisories for CVE-2026-52858(7)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.0.1453-1ubuntu1.13+esm20) @ bionic2026-08-20ubuntu
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
redhatvim-2:9.1.083-5.el10_0.42026-08-17redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatvim-2:8.0.1763-27.el8_102026-07-13redhat
redhatvim-2:8.2.2637-26.el9_8.102026-07-13redhat
redhatvim-2:9.1.083-9.el10_2.72026-07-13redhat

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
vim—9.2.0498-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(3)

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 22× in last 7d / 92× 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 209 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-52858?
CVE-2026-52858 is a high vulnerability published on June 11, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0561, the Python omni-completion script in python3complete.vim for Vim with the +python3 interpreter enabled (and the legacy pythoncomplete.vim for builds with the +python interpreter) executes the import and from statements…
When was CVE-2026-52858 disclosed?
CVE-2026-52858 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52858 actively exploited?
CVE-2026-52858 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 89.6% of all scored CVEs.
What is the CVSS score of CVE-2026-52858?
CVE-2026-52858 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52858?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52858, 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-52858

Explore →

Is Your Infrastructure Affected by CVE-2026-52858?

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

Start Free Scan →Browse All CVEs