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 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
Trending — 5 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
3.5%
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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuvim-tiny (2:7.4.052-1ubuntu3.1+esm31) @ trusty2026-07-15ubuntu
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.

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 29× in last 7d / 29× 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.

  1. 2026-07-15 18:41 UTCEG score recompute
  2. 2026-07-15 18:41 UTCVendor advisory
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 07:03 UTCEG score recompute
  6. 2026-07-15 07:03 UTCVendor advisory
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 02:00 UTCEPSS rescore
  9. 2026-07-14 19:24 UTCEG score recompute
  10. 2026-07-14 07:43 UTCEG score recompute
  11. 2026-07-14 06:00 UTCNVD updateCVSS v3 → 7.8
  12. 2026-07-14 04:25 UTCMITRE cvelistV5CVSS v3 → 8.4
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 19:59 UTCEG score recompute
  15. 2026-07-13 08:20 UTCEG score recompute
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 20:40 UTCEG score recompute
  19. 2026-07-12 08:59 UTCEG score recompute
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-11 21:20 UTCEG score recompute
  22. 2026-07-11 09:42 UTCEG score recompute
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-10 22:03 UTCEG score recompute▼ 0.60
Show 4 more
  1. 2026-07-10 20:19 UTCNVD updateCVSS v3 → 7.8
  2. 2026-07-10 10:25 UTCEG score recompute
  3. 2026-07-09 22:46 UTCEG score recompute
  4. 2026-07-09 22:45 UTCMITRE cvelistV5first tracked

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 3.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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