CVE-2022-25893

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-12-21. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2022-7507 (ENISA EUVD) · GHSA-4w2j-2rg4-5mjw (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

The package vm2 before 3.9.10 are vulnerable to Arbitrary Code Execution due to the usage of prototype lookup for the WeakMap.prototype.set method. Exploiting this vulnerability leads to access to a host object and a sandbox compromise.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
1.5%
EPSS %ILE
75th
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-12). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

December 21, 2022

Last Modified

April 15, 2025

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_pr.
Web page

Arbitrary Code Execution in vm2 | CVE-2022-25893 | Snyk

https://security.snyk.io/vuln/SNYK-JS-VM2-2990237
GitHub pull request Patch Available

Security fix for issue 444.

Patch available: patriksimek/vm2 3.9.10 (PR #445 merged 2022-07-05)

https://github.com/patriksimek/vm2/pull/445/commits/3a9876482be487b78a90ac459675da7f83f46d69
GitHub pull request Patch Available

Security fix for issue 444.

Patch available: patriksimek/vm2 3.9.10 (PR #445 merged 2022-07-05)

https://github.com/patriksimek/vm2/pull/445
Web page

Security Issue · Issue #444 · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/issues/444

Vendor Advisories for CVE-2022-25893(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 / EcosystemFix (by version range) / PatchReleasedSource
npmvm2 @ 3.9.10 (fixes < 3.9.10)—ghsa

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
vm2—
  • every version up to 3.9.10: fixed in 3.9.10
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 255 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 155 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-25893?
CVE-2022-25893 is a critical-severity vulnerability; its CVE record was published on December 21, 2022. The package vm2 before 3.9.10 are vulnerable to Arbitrary Code Execution due to the usage of prototype lookup for the WeakMap.prototype.set method. Exploiting this vulnerability leads to access to a host object and a sandbox compromise.
When was CVE-2022-25893 made public?
CVE-2022-25893 was made public on December 21, 2022: that is the date its CVE record's CNA, Snyk, gives for when the vulnerability was made public. The CVE record itself was published on December 21, 2022. EchelonGraph's copy of the record carries a last-modified date of April 15, 2025; the record at its source may have been updated since.
Is CVE-2022-25893 actively exploited?
CVE-2022-25893 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (75th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-25893?
CVE-2022-25893 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-25893?
A fix for CVE-2022-25893 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-25893 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-2022-25893

Explore →

Is Your Infrastructure Affected by CVE-2022-25893?

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

Book a Demo →Browse All CVEs