{"answers":{"affected":"2 open source packages ship an affected version, including isolated-vm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21413 in the wild and no public exploit code.","fix":"Upgrade isolated-vm to 4.0.0 or later.","what":"CVE-2021-21413 is a high-severity vulnerability in laverdet isolated-vm, published on 30 Mar 2021. 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-2021-21413 and fix it if it is affected.\n\nWhat it is: CVE-2021-21413 is a high-severity vulnerability in laverdet isolated-vm, published on 30 Mar 2021. 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-2021-21413 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- isolated-vm (npm): affected all versions; fixed in 4.0.0\n- isolated-vm (npm): affected all versions; fixed in 4.0.0\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-2021-21413/ (Markdown: https://insights.sbomify.com/CVE-2021-21413/index.md)","id":"CVE-2021-21413","markdown":"https://insights.sbomify.com/CVE-2021-21413/index.md","name":"CVE-2021-21413","record":{"aliases":["GHSA-mmhj-4w6j-76h7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js VM library","requires_auth":"none","summary":"Attackers can escape isolated VM contexts to access the main Node.js isolate, potentially executing arbitrary code via native module loading.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"isolated-vm","vendor":"isolated-vm_project"}],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"isolated-vm is a library for nodejs which gives you access to v8's Isolate interface. Versions of isolated-vm before v4.0.0 have API pitfalls which may make it easy for implementers to expose supposed secure isolates to the permissions of the main nodejs isolate. Reference objects allow access to the underlying reference's full prototype chain. In an environment where the implementer has exposed a Reference instance to an attacker they would be able to use it to acquire a Reference to the nodejs context's Function object. Similar application-specific attacks could be possible by modifying the local prototype of other API objects. Access to NativeModule objects could allow an attacker to load and run native code from anywhere on the filesystem. If combined with, for example, a file upload API this would allow for arbitrary code execution. This is addressed in v4.0.0 through a series of related changes.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-10-14","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-14T00:15:35Z","kind":"github_poc","ref":"https://github.com/sm1ee/CVE-2021-21413","stars":0,"title":"CVE-2021-21413 isotaled-vm Sandbox Escape PoC"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate","id":"CVE-2021-21413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"privilege_escalation","year":"2021"},"n_packages":2,"n_references":4,"next":{"headline":"Command injection vulnerability in @prisma/sdk in getPackedPackage function","id":"CVE-2021-21414"},"packages":[{"ecosystem":"npm","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"isolated-vm","purl":null,"source":"GHSA-mmhj-4w6j-76h7"},{"ecosystem":"npm","fixed":["4.0.0"],"introduced":["0"],"last_affected":[],"package":"isolated-vm","purl":"pkg:npm/isolated-vm","source":"GHSA-mmhj-4w6j-76h7"}],"prev":{"headline":"[thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property values","id":"CVE-2021-21412"},"products":["isolated-vm"],"published":"2021-03-30","related":[{"cvss_score":9.7,"headline":"isolated-vm has vulnerable CachedDataOptions in API","id":"CVE-2022-39266","kev_date_added":null,"published":"2022-09-29"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["laverdet"]},"summary":"Attackers can escape isolated VM contexts to access the main Node.js isolate, potentially executing arbitrary code via native module loading.","url":"https://insights.sbomify.com/CVE-2021-21413/"}