CVE-2026-44656

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 42% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to version 9.2.0435, an OS command injection vulnerability exists in Vim's :find command-line completion. When the path option contains backtick-enclosed shell commands, those commands are executed during file name completion. Because the path option lacks the P_SECURE flag, it can be set from a modeline, allowing an attacker who controls the contents of a file to execute arbitrary shell commands when the user opens that file in Vim and triggers :find completion. This issue has been patched in version 9.2.0435.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

May 8, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
Patch available. Sources: github_commit, github.
github Patch Available

OS Command Injection via 'path' completion affects Vim < 9.2.0435 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-hwg5-3cxw-wvvg
github_commit

commit 190cb3c2b9c7 (vim/vim)

Fix landed in vim/vim commit 190cb3c2b9c7 — awaiting tagged release

https://github.com/vim/vim/commit/190cb3c2b9c769a3972bcfd991a7b5b6cb771ef0

Vendor Advisories for CVE-2026-44656(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.14) @ noble2026-08-23ubuntu

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 rangeFixed inDependents
vim—9.2.0437-r0—
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.0428-1 (15 versions)2:9.2.0461-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 5× in last 7d / 48× 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 168 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44656?
CVE-2026-44656 is a medium vulnerability published on May 8, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0435, an OS command injection vulnerability exists in Vim's :find command-line completion. When the path option contains backtick-enclosed shell commands, those commands are executed during file name completion. Because the path…
When was CVE-2026-44656 disclosed?
CVE-2026-44656 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44656 actively exploited?
CVE-2026-44656 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.1% of all scored CVEs.
What is the CVSS score of CVE-2026-44656?
CVE-2026-44656 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44656?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44656, 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-44656

Explore →

Is Your Infrastructure Affected by CVE-2026-44656?

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

Start Free Scan →Browse All CVEs