CVE-2022-2042

CRITICALNVD 7.89.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-06-11. NVD baseline CVSS 7.8; sources differ by 2.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2022-34345 (ENISA EUVD) · GHSA-jx8j-jfm7-h5wj (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use After Free in GitHub repository vim/vim prior to 8.2.

CVSS v3
7.8
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.5%
EPSS %ILE
74th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 10, 2022

Last Modified

October 8, 2026

Advisory Details (10)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit.
Web page

Full Disclosure: APPLE-SA-2022-10-27-9 Additional information for APPLE-SA-2022-09-12-3 macOS Big Sur 11.7

http://seclists.org/fulldisclosure/2022/Oct/45
Web page

Full Disclosure: APPLE-SA-2022-10-27-7 Additional information for APPLE-SA-2022-09-12-4 macOS Monterey 12.6

http://seclists.org/fulldisclosure/2022/Oct/43
Web page

Full Disclosure: APPLE-SA-2022-10-24-2 macOS Ventura 13

http://seclists.org/fulldisclosure/2022/Oct/28
Web page

Full Disclosure: APPLE-SA-2022-10-27-5 Additional information for APPLE-SA-2022-10-24-2 macOS Ventura 13

http://seclists.org/fulldisclosure/2022/Oct/41
Web page

About the security content of macOS Ventura 13 - Apple Support

https://support.apple.com/kb/HT213488
Web page

About the security content of macOS Monterey 12.6 - Apple Support

https://support.apple.com/kb/HT213444
Web page

About the security content of macOS Big Sur 11.7 - Apple Support

https://support.apple.com/kb/HT213443
Web page

Vim, gVim: Multiple Vulnerabilities (GLSA 202208-32) — Gentoo security

https://security.gentoo.org/glsa/202208-32
GitHub commit

commit 2813f38e021c (vim/vim)

Fix landed in vim/vim commit 2813f38e021c — awaiting tagged release

https://github.com/vim/vim/commit/2813f38e021c6e6581c0c88fcf107e41788bc835
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/8628b4cd-4055-4059-aed4-64f7fdc10eba

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuvim-runtime (2:7.4.1689-3ubuntu1.5+esm7) @ xenial2026-11-02ubuntu
ubuntuvim-tiny (2:7.4.052-1ubuntu3.1+esm15) @ trusty2026-11-02ubuntu

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 rangeFix by version rangeDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
vim—
  • every version up to 2:9.0.0135-1: fixed in 2:9.0.0135-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
vim—
  • every version up to 2:9.0.0135-1: fixed in 2:9.0.0135-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vim—
  • every version up to 2:9.0.0135-1: fixed in 2:9.0.0135-1
—

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 31× in last 7d / 94× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 275 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 175 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-2042?
CVE-2022-2042 is a critical-severity vulnerability; its CVE record was published on June 10, 2022. Use After Free in GitHub repository vim/vim prior to 8.2.
When was the CVE record for CVE-2022-2042 published?
The CVE record for CVE-2022-2042 was published on June 10, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2022-2042 actively exploited?
CVE-2022-2042 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (74th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-2042?
CVE-2022-2042 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-2042?
A fix for CVE-2022-2042 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-2042

Explore →

Is Your Infrastructure Affected by CVE-2022-2042?

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