{"answers":{"affected":"4 open source packages ship an affected version, including @enclave-vm/core and enclave-vm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25533 in the wild and no public exploit code.","fix":"Upgrade @enclave-vm/core to 2.10.1 or later.","what":"CVE-2026-25533 is a medium-severity code injection vulnerability in agentfront enclave, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25533 and fix it if it is affected.\n\nWhat it is: CVE-2026-25533 is a medium-severity code injection vulnerability in agentfront enclave, published on 6 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25533 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @enclave-vm/core (npm): affected all versions; fixed in 2.10.1\n- @enclave-vm/core (npm): affected all versions; fixed in 2.10.1\n- enclave-vm (npm): affected all versions up to 2.7.0; no fix listed\n- enclave-vm (npm): affected all versions up to 2.7.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25533/ (Markdown: https://insights.sbomify.com/CVE-2026-25533/index.md)","id":"CVE-2026-25533","markdown":"https://insights.sbomify.com/CVE-2026-25533/index.md","name":"CVE-2026-25533","record":{"aliases":["GHSA-x39w-8vm5-5m3p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JavaScript sandbox library","requires_auth":"none","summary":"Attackers can escape the Enclave JavaScript sandbox via recursion and error object exploits, enabling arbitrary code execution on the host.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"enclave","vendor":"agentfront"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"Enclave is a secure JavaScript sandbox designed for safe AI agent code execution. Prior to 2.10.1, the existing layers of security in enclave-vm are insufficient: The AST sanitization can be bypassed with dynamic property accesses, the hardening of the error objects does not cover the peculiar behavior or the vm module and the function constructor access prevention can be side-stepped by leveraging host object references. This vulnerability is fixed in 2.10.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Enclave has a sandbox escape via infinite recursion and error objects","id":"CVE-2026-25533","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"Spinnaker clouddriver and orca URL validation bypass via underscores in hostnames","id":"CVE-2026-25534"},"packages":[{"ecosystem":"npm","fixed":["2.10.1"],"introduced":["0"],"last_affected":[],"package":"@enclave-vm/core","purl":null,"source":"GHSA-x39w-8vm5-5m3p"},{"ecosystem":"npm","fixed":["2.10.1"],"introduced":["0"],"last_affected":[],"package":"@enclave-vm/core","purl":"pkg:npm/%40enclave-vm/core","source":"GHSA-x39w-8vm5-5m3p"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.7.0"],"package":"enclave-vm","purl":null,"source":"GHSA-x39w-8vm5-5m3p"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.7.0"],"package":"enclave-vm","purl":"pkg:npm/enclave-vm","source":"GHSA-x39w-8vm5-5m3p"}],"prev":{"headline":"ESF-IDF is Vulnerable to WPS Enrollee Fragment Integer Underflow","id":"CVE-2026-25532"},"products":["enclave"],"published":"2026-02-06","related":[{"cvss_score":10,"headline":"@enclave-vm/core is vulnerable to Sandbox Escape","id":"CVE-2026-27597","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":10,"headline":"Sandbox Escape via Host Error Prototype Chain in enclave-vm","id":"CVE-2026-22686","kev_date_added":null,"published":"2026-01-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-09","vendors":["agentfront"]},"summary":"Attackers can escape the Enclave JavaScript sandbox via recursion and error object exploits, enabling arbitrary code execution on the host.","url":"https://insights.sbomify.com/CVE-2026-25533/"}