CVE-2026-55895

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 87% 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 — 3 sources updated 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.0663, a Vimscript code injection vulnerability exists in s:NetrwLocalRmFile() in the netrw plugin (runtime/pack/dist/opt/netrw/autoload/netrw.vim) when deleting a local file from the browser. A filename derived from the buffer's directory listing is interpolated into an Ex command line passed to :execute with only the backslash character escaped, allowing a crafted filename containing a bar (|) to terminate the intended command and execute arbitrary Vimscript, including shell commands via :call system() and :!. This vulnerability is fixed in 9.2.0663.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
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.
github Patch Available

Vimscript Code Injection in netrw NetrwLocalRmFile() via crafted filename affects Vim < 9.2.0663 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-vhh8-v6wx-hjjh
github_commit

commit 55bc757a5d43 (vim/vim)

Fix landed in vim/vim commit 55bc757a5d43 — awaiting tagged release

https://github.com/vim/vim/commit/55bc757a5d436e59d50fe43f7cda94b118f86cb2

Vendor Advisories for CVE-2026-55895(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuxxd (2:9.1.0016-1ubuntu7.17) @ noble2026-08-30ubuntu

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(2)

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 11× in last 7d / 88× 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 191 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55895?
CVE-2026-55895 is a high vulnerability published on June 25, 2026. Vim is an open source, command line text editor. Prior to 9.2.0663, a Vimscript code injection vulnerability exists in s:NetrwLocalRmFile() in the netrw plugin (runtime/pack/dist/opt/netrw/autoload/netrw.vim) when deleting a local file from the browser. A filename derived from the buffer's…
When was CVE-2026-55895 disclosed?
CVE-2026-55895 was first published in the National Vulnerability Database 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-55895 actively exploited?
CVE-2026-55895 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 86.8% of all scored CVEs.
What is the CVSS score of CVE-2026-55895?
CVE-2026-55895 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-55895?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55895, 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-55895

Explore →

Is Your Infrastructure Affected by CVE-2026-55895?

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

Start Free Scan →Browse All CVEs