Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@enclave-vm/core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 10.0npmAmendedPublished

    @enclave-vm/core is vulnerable to Sandbox Escape

    CVE-2026-27597 · GHSA-f229-3862-4942

    Affected
    • npm @enclave-vm/core <= 2.10.1
    Fixed in
    2.11.1· Vendor fix available
    Issue
    It is possible to escape the security boundraries set by @enclave-vm/core, which can be used to achieve remote code execution (RCE). The issue has been fixed in version 2.11.1. --- Details It is possible to obtain the native Object constructor (instead of the SafeObject wrapper). This can be used to get retrieve property descriptors via Object.getOwnPropertyDescriptors, allowing access to properties otherwise restricted by the sandbox. When a memory limit is set (which is the default), hostmemorytrack, a host object, can be used to escape via the host function constructor. When this is not the case, a host reference can be obtained via Node's nodejs.util.inspect.custom symbol (which can be triggered, for example, through console.log). --- Proof of Concept PoC 1 --- PoC 2 --- Impact This vulnerability allows a malicious actor executing untrusted code inside an Enclave instance to escape the sandbox and execute arbitrary commands on the host system. This constitutes Remote Code…

    Recommended action: Upgrade to 2.11.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.com (1)osv.dev (2)Source checked Evidence →