major vulnerability· requires attention

Widespread Node.js sandbox library vm2; RCE sandbox escape in many applications handling untrusted code — high-impact and newsworthy.

Applications

CVE-2026-92939

9.4

Critical

EPSS 0.62%Patch available

vm2 sandbox escape enabling native code execution via crypto.setEngine().

exploited

Public proof of concept per CISA SSVC; not in CISA KEV

fix

Fixed in 3.11.7

likelihood

EPSS 0.62%top 51% of scored CVEs

Published 17 Sept 2026Analysed here 19 Sept 2026CVSS scored by the publisher (CNA)

do firstUpgrade to a fixed release: 3.11.7.

common questions

Is CVE-2026-92939 being exploited?

Not confirmed. CVE-2026-92939 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.

How severe is CVE-2026-92939?

CVE-2026-92939 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-92939?

Yes. A fix has been recorded for CVE-2026-92939. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-92939 affect?

CVE-2026-92939 affects vm2 3.11.3 - 3.11.6, Node.js apps using vm2 with crypto builtin allowed, Environments running untrusted plugins or code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-92939?

Upgrade vm2 to >=3.11.7, disable/deny crypto builtin for untrusted sandboxes, audit and rotate secrets.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

vm2 3.11.3 - 3.11.6Node.js apps using vm2 with crypto builtin allowedEnvironments running untrusted plugins or code

impact

Sandboxed JS can load attacker native libraries via crypto.setEngine(), causing host-process native code execution and full RCE.

action required

Immediate action required

affected versions

patriksimek vm2

affected>= 3.11.3 and < 3.11.7

vendor says fixed in3.11.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation: poc
automatable: no
technical impact: total

Assessed by CISA 17 Sept 2026 (SSVC 2.0.3).

timeline

17 Sept 2026Published
17 Sept 2026CISA SSVC assessment: exploitation poc · same day later
17 Sept 2026CVE record last updated · same day later
19 Sept 2026Analysed by vulneraibility.com · 2 days later

also known as

GHSA-46pr-c5wc-xffx

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

2 references in the CVE record: 2 advisories

Advisorygithub.com /patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx
Advisoryvulncheck.com /advisories/vm2-3.11.3-through-3.11.6-native-code-execution-via-crypto-setengine

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
OSV: advisory aliases and downstream package versions
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free