CVE-2026-43998

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% 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, secondary
Elevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. In 3.10.5, NodeVM's require.root path restriction can be bypassed using filesystem symlinks, allowing sandboxed code to load modules from outside the allowed root directory in host context. Because path validation uses path.resolve() (which does not dereference symlinks) but module loading uses Node's native require() (which does), an attacker can load arbitrary host-realm modules and achieve remote code execution. This vulnerability is fixed in 3.11.0.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
54(Track*)
EG Risk 54/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
Severity85% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

May 13, 2026

Last Modified

September 7, 2026

Advisory Details (1)

Auto-updated May 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

NodeVM require.root bypass via symlink traversal allows sandbox escape · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-cp6g-6699-wx9c

Vendor Advisories for CVE-2026-43998(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
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat

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 rangeFixed inDependents
vm23.10.53.11.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 37× 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 172 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43998?
CVE-2026-43998 is a high vulnerability published on May 13, 2026. vm2 is an open source vm/sandbox for Node.js. In 3.10.5, NodeVM's require.root path restriction can be bypassed using filesystem symlinks, allowing sandboxed code to load modules from outside the allowed root directory in host context. Because path validation uses path.resolve() (which does not…
When was CVE-2026-43998 disclosed?
CVE-2026-43998 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on September 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43998 actively exploited?
CVE-2026-43998 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 48.0% of all scored CVEs.
What is the CVSS score of CVE-2026-43998?
CVE-2026-43998 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-43998?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43998, 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-43998

Explore →

Is Your Infrastructure Affected by CVE-2026-43998?

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

Start Free Scan →Browse All CVEs