CVE-2026-45411 affects the vm2 Node.js sandbox, a tool used for creating isolated JavaScript environments. This vulnerability allows attackers to escape the sandbox and execute arbitrary commands on the host system, potentially leading to complete system compromise. The vulnerability impacts versions 0.0.0 up to and including 3.11.2. A fix is available in version 3.11.3.
影响与攻击场景翻译中…
The impact of CVE-2026-45411 is severe. Successful exploitation allows an attacker to bypass the intended isolation of the vm2 sandbox and gain direct access to the host system. This could involve executing malicious code, stealing sensitive data, installing malware, or establishing persistent backdoors. The ability to execute arbitrary commands effectively grants the attacker complete control over the affected system. This vulnerability shares similarities with sandbox escape vulnerabilities where improper exception handling leads to privilege escalation and code execution outside the intended boundaries.
利用背景翻译中…
CVE-2026-45411 was published on 2026-05-13. Its severity is rated CRITICAL (CVSS 9.8). Exploitation context is currently limited, with no known active campaigns or widespread exploitation. Public proof-of-concept (POC) code is likely to emerge given the vulnerability's severity and ease of exploitation. It is not currently listed on KEV or EPSS, but the high CVSS score suggests a medium to high probability of exploitation if a POC is released.
威胁情报
漏洞利用状态
CISA SSVC
CVSS 向量
这些指标意味着什么?
- Attack Vector
- 网络 — 可通过互联网远程利用,无需物理或本地访问。攻击面最大。
- Attack Complexity
- 低 — 无需特殊条件,可以稳定地利用漏洞。
- Privileges Required
- 无 — 无需认证,无需凭证即可利用。
- User Interaction
- 无 — 攻击自动且无声,受害者无需任何操作。
- Scope
- 未改变 — 影响仅限于脆弱组件本身。
- Confidentiality
- 高 — 完全丧失机密性,攻击者可读取所有数据。
- Integrity
- 高 — 攻击者可写入、修改或删除任何数据。
- Availability
- 高 — 完全崩溃或资源耗尽,完全拒绝服务。
受影响的软件
弱点分类 (CWE)
时间线
- 已保留
- 发布日期
缓解措施和替代方案翻译中…
The primary mitigation for CVE-2026-45411 is to immediately upgrade to vm2 version 3.11.3 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider implementing a temporary workaround by carefully reviewing and sanitizing any user-provided code executed within the vm2 sandbox. While not a complete solution, restricting the permissions of the process running vm2 can limit the potential damage. Monitor system logs for unusual activity or errors related to vm2, which could indicate exploitation attempts. After upgrading, confirm the fix by attempting to trigger the vulnerability with known exploit patterns and verifying that the sandbox remains intact.
修复方法翻译中…
Actualice a la versión 3.11.3 o superior para mitigar la vulnerabilidad. Esta versión corrige el problema al manejar correctamente las excepciones dentro de los generadores asíncronos, evitando la posibilidad de escape del sandbox.
常见问题翻译中…
What is CVE-2026-45411 — RCE in vm2 Node.js Sandbox?
CVE-2026-45411 is a critical Remote Code Execution (RCE) vulnerability in the vm2 Node.js sandbox, allowing attackers to escape the sandbox and execute arbitrary code on the host system. It affects versions 0.0.0 through 3.11.2.
Am I affected by CVE-2026-45411 in vm2?
Yes, if you are using vm2 versions 0.0.0 through 3.11.2, you are vulnerable to this RCE. Immediately check your installed version and upgrade if necessary.
How do I fix CVE-2026-45411 in vm2?
The recommended fix is to upgrade to vm2 version 3.11.3 or later. This version includes a patch that addresses the vulnerability. If immediate upgrade is not possible, consider temporary workarounds like code review and permission restrictions.
Is CVE-2026-45411 being actively exploited?
Currently, there are no confirmed reports of active exploitation. However, given the vulnerability's severity and potential impact, exploitation is likely if a public proof-of-concept is released.
Where can I find the official vm2 advisory for CVE-2026-45411?
Refer to the vm2 project's GitHub repository and associated security advisories for the latest information and updates regarding CVE-2026-45411: [https://github.com/vm2js/vm2](https://github.com/vm2js/vm2)
立即试用 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...