CVE-2026-57456

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% 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.1%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 9.2.0699, Vim's Python omni-completion (runtime/autoload/python3complete.vim and the legacy pythoncomplete.vim) executes reconstructed function and class definitions from the current buffer with exec() as part of populating the completion dictionary. When reconstructing that source, each scope's docstring is inserted verbatim between triple quotes with no escaping, so a hostile buffer can break out of the triple-quoted literal and execute attacker-controlled Python during omni-completion. This vulnerability is fixed in 9.2.0699.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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%
Automatability30% × 15%
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github_commit, github.
githubMentions a patch (unverified)

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

https://github.com/vim/vim/security/advisories/GHSA-ppj8-wqjf-6fp3
github_commit

commit cce141c42740 (vim/vim)

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

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuxxd (2:9.1.0967-1ubuntu6.8) @ questing2026-09-23ubuntu
redhatvim-2:7.4.629-5.el6_10.42026-09-21redhat
redhatvim-2:7.4.629-8.el7_9.22026-09-17redhat
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
redhatrhui5/rhua-rhel9:17865335292026-08-12redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17864336562026-08-11redhat
redhatvim-2:8.0.1763-31.el8_102026-07-31redhat
redhatvim-2:9.1.083-9.el10_2.122026-07-31redhat
redhatvim-2:8.2.2637-26.el9_8.132026-07-29redhat
redhatvim-main-9.2.780-1.hum12026-07-03redhat

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.0854-r0: fixed in 9.2.0854-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(1)

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

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 6× in last 7d / 33× 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 238 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-57456?
CVE-2026-57456 is a high vulnerability published on June 25, 2026. Vim is an open source, command line text editor. Prior to 9.2.0699, Vim's Python omni-completion (runtime/autoload/python3complete.vim and the legacy pythoncomplete.vim) executes reconstructed function and class definitions from the current buffer with exec() as part of populating the completion…
When was CVE-2026-57456 disclosed?
CVE-2026-57456 was first published on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57456 actively exploited?
CVE-2026-57456 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57456?
CVE-2026-57456 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-57456?
A fix for CVE-2026-57456 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57456 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-57456

Explore →

Is Your Infrastructure Affected by CVE-2026-57456?

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