CVE-2026-59858

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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 9.2.0735, the C omni-completion script in runtime/autoload/ccomplete.vim interpolates the typeref: or typename: extension field of a tags entry, without escaping, into a :vimgrep pattern that is run through :execute. Because :vimgrep honors the bar as a command separator, a crafted tag field can close the search pattern and append an arbitrary Ex command; opening a hostile .c file whose project tags file contains such an entry and invoking C omni-completion runs that command as the editing user. This issue is fixed in version 9.2.0735.

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

Published

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 9, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

Arbitrary Code Execution via C Omni-Completion in Vim < 9.2.0735 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-mf92-v4xw-j45x
github_commit

commit 6b611b0d1560 (vim/vim)

Fix landed in vim/vim commit 6b611b0d1560 — awaiting tagged release

https://github.com/vim/vim/commit/6b611b0d15603c52ebdad17172b0232b4f65704e

Vendor Advisories for CVE-2026-59858(9)

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

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:8.0.1453-1ubuntu1.13+esm22) @ bionic2026-08-30ubuntu
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

(4 across 4 ecosystems)
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 18× in last 7d / 106× 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 164 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59858?
CVE-2026-59858 is a high vulnerability published on July 9, 2026. Vim is an open source, command line text editor. Prior to 9.2.0735, the C omni-completion script in runtime/autoload/ccomplete.vim interpolates the typeref: or typename: extension field of a tags entry, without escaping, into a :vimgrep pattern that is run through :execute. Because :vimgrep honors…
When was CVE-2026-59858 disclosed?
CVE-2026-59858 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59858 actively exploited?
CVE-2026-59858 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 96.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59858?
CVE-2026-59858 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-59858?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59858, 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-59858

Explore →

Is Your Infrastructure Affected by CVE-2026-59858?

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

Start Free Scan →Browse All CVEs