CVE-2026-73070

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). 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
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to 9.2.0842, the socket server backend in src/socketserver.c accepts unbounded client connections in socketserver_accept(), causing descriptors to overflow fd_set structures in src/channel.c and fixed-size struct pollfd arrays in src/os_unix.c, which allows a local process that can connect to the server socket to corrupt stack memory or terminate the Vim server. This issue is fixed in version 9.2.0842.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100CISA SSVC

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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: github, github_commit.
github_commit

commit 5598618b2daf (vim/vim)

Fix landed in vim/vim commit 5598618b2daf — awaiting tagged release

https://github.com/vim/vim/commit/5598618b2daf8e36b3bf0251caaefcf0bf8e85e4
github Patch Available

Stack Buffer Overflow in the Vim Socket Server in Vim < 9.2.0842 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-49m8-wwxj-mr69

Vendor Advisories for CVE-2026-73070(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatvim-main-9.2.967-1.hum12026-08-19redhat

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)
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: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.0782-1 (18 versions)
  • every version up to 2:9.2.0858-1: fixed in 2:9.2.0858-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 69× 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 135 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73070?
CVE-2026-73070 is a medium vulnerability published on August 11, 2026. Vim is an open source, command line text editor. Prior to 9.2.0842, the socket server backend in src/socketserver.c accepts unbounded client connections in socketserveraccept(), causing descriptors to overflow fdset structures in src/channel.c and fixed-size struct pollfd arrays in src/os_unix.c,…
When was CVE-2026-73070 disclosed?
CVE-2026-73070 was first published on August 11, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73070 actively exploited?
CVE-2026-73070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73070?
CVE-2026-73070 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-73070?
A fix for CVE-2026-73070 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73070 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-73070

Explore →

Is Your Infrastructure Affected by CVE-2026-73070?

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

Book a Demo →Browse All CVEs