CVE-2026-22709

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
10.0EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. In vm2 prior to version 3.10.2, Promise.prototype.then Promise.prototype.catch callback sanitization can be bypassed. This allows attackers to escape the sandbox and run arbitrary code. In lib/setup-sandbox.js, the callback function of localPromise.prototype.then is sanitized, but globalPromise.prototype.then is not sanitized. The return value of async functions is globalPromise object. Version 3.10.2 fixes the issue.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation1.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (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.3%
EPSS %ILE
69th
KEV
Not listed

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

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

Exploitation none (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.

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

January 26, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Oct 13, 2026
Patch available. Sources: github_release, github, github_commit.
GitHub advisoryMentions a patch (unverified)

Sandbox Escape · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-99p7-6v5w-7xg8
GitHub release Patch Available

v3.10.2

Patch available: patriksimek/vm2 v3.10.2

https://github.com/patriksimek/vm2/releases/tag/v3.10.2
GitHub commit Patch Available

commit 4b009c2d4b11 (patriksimek/vm2)

Patch available: patriksimek/vm2 v3.10.2 (contains commit 4b009c2d4b11)

https://github.com/patriksimek/vm2/commit/4b009c2d4b1131c01810c1205e641d614c322a29

Affected Packages

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 32× 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 93 of 176 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-22709?
CVE-2026-22709 is a critical-severity vulnerability; its CVE record was published on January 26, 2026. vm2 is an open source vm/sandbox for Node.js. In vm2 prior to version 3.10.2, Promise.prototype.then Promise.prototype.catch callback sanitization can be bypassed. This allows attackers to escape the sandbox and run arbitrary code. In lib/setup-sandbox.js, the callback function of…
When was the CVE record for CVE-2026-22709 published?
The CVE record for CVE-2026-22709 was published on January 26, 2026. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-22709 actively exploited?
CVE-2026-22709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (69th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22709?
CVE-2026-22709 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-22709?
A fix for CVE-2026-22709 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-2026-22709

Explore →

Is Your Infrastructure Affected by CVE-2026-22709?

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

Book a Demo →Browse All CVEs