CVE-2026-47139

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM supports excluding public network builtins from the wildcard builtin option. With this configuration direct access to http, https, http2, net, dgram, tls, dns, and dns/promises is blocked. However, Node.js also exposes underscored internal HTTP builtins such as _http_client and _http_server. These are not blocked when the public modules are excluded. Sandboxed code can use these internal builtins to make outbound HTTP requests and open listening HTTP sockets even though the public network modules are denied. This issue has been patched in version 3.11.4.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity86% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 12, 2026

Advisory Details (3)

Auto-updated Jun 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

NodeVM network builtin exclusions bypass via internal _http_client and _http_server · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-r9pm-gxmw-wv6p
github_release Patch Available

v3.11.4

Patch available: patriksimek/vm2 v3.11.4

https://github.com/patriksimek/vm2/releases/tag/v3.11.4
github_commit Patch Available

commit 436053e30eec (patriksimek/vm2)

Patch available: patriksimek/vm2 v3.11.4 (contains commit 436053e30eec)

https://github.com/patriksimek/vm2/commit/436053e30eecbabd487e2fd2959c137ac34e2bb1

Vendor Advisories for CVE-2026-47139(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatansible-automation-platform/automation-portal:17858542262026-08-05redhat
redhatrhdh/rhdh-hub-rhel9:17834481842026-07-08redhat
redhatrhdh/rhdh-hub-rhel9:17827612442026-06-30redhat

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
vm2—3.11.4—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 75× 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 154 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47139?
CVE-2026-47139 is a high vulnerability published on May 29, 2026. vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM supports excluding public network builtins from the wildcard builtin option. With this configuration direct access to http, https, http2, net, dgram, tls, dns, and dns/promises is blocked. However, Node.js also exposes…
When was CVE-2026-47139 disclosed?
CVE-2026-47139 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47139 actively exploited?
CVE-2026-47139 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.7% of all scored CVEs.
What is the CVSS score of CVE-2026-47139?
CVE-2026-47139 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-47139?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47139, 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-47139

Explore →

Is Your Infrastructure Affected by CVE-2026-47139?

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

Start Free Scan →Browse All CVEs