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
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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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%
EPSS PROB
0.2%
EPSS %ILE
9th
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(20)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuxxd (2:8.0.1453-1ubuntu1.13+esm20) @ bionic2026-09-14ubuntu
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
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.2.2637-26.el9_8.102026-07-13redhat
redhatvim-2:9.1.083-9.el10_2.72026-07-13redhat
redhatvim-2:8.0.1763-27.el8_102026-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 rangeFix by version rangeDependents
vim—
  • every version up to 9.2.0498-r0: fixed in 9.2.0498-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vim2:9.1.1230-2 ... 2:9.2.0524-1 (17 versions)
  • every version up to 2:9.2.0782-1: fixed in 2:9.2.0782-1
—

Weakness Classification(3)

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

All Vendor Advisories

(9)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 24× 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 254 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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.2% probability of exploitation in the next 30 days (9th percentile of EPSS-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?
A fix for CVE-2026-52858 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52858 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs