{"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-2022-39266 in the wild and no public exploit code.","fix":"Upgrade isolated-vm to 4.3.7 or later.","what":"CVE-2022-39266 is a critical code injection vulnerability in laverdet isolated-vm, published on 29 Sep 2022. 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-2022-39266 and fix it if it is affected.\n\nWhat it is: CVE-2022-39266 is a critical code injection vulnerability in laverdet isolated-vm, published on 29 Sep 2022. 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-2022-39266 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- isolated-vm (npm): affected all versions; fixed in 4.3.7\n- isolated-vm (npm): affected all versions; fixed in 4.3.7\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-2022-39266/ (Markdown: https://insights.sbomify.com/CVE-2022-39266/index.md)","id":"CVE-2022-39266","markdown":"https://insights.sbomify.com/CVE-2022-39266/index.md","name":"CVE-2022-39266","record":{"aliases":["GHSA-2jjq-x548-rhpv"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Node.js VM library","requires_auth":"none","summary":"Attackers can bypass the sandbox and execute arbitrary code in the Node.js process by providing malicious cached data to the isolated-vm library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"isolated-vm","vendor":"isolated-vm_project"}],"cvss":{"score":9.7,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"isolated-vm is a library for nodejs which gives the user access to v8's Isolate interface. In versions 4.3.6 and prior, if the untrusted v8 cached data is passed to the API through CachedDataOptions, attackers can bypass the sandbox and run arbitrary code in the nodejs process. Version 4.3.7 changes the documentation to warn users that they should not accept `cachedData` payloads from a user.","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":"isolated-vm has vulnerable CachedDataOptions in API","id":"CVE-2022-39266","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"Brokercap Bifrost vulnerable to authentication bypass for admin and monitor user groups","id":"CVE-2022-39267"},"packages":[{"ecosystem":"npm","fixed":["4.3.7"],"introduced":["0"],"last_affected":[],"package":"isolated-vm","purl":null,"source":"GHSA-2jjq-x548-rhpv"},{"ecosystem":"npm","fixed":["4.3.7"],"introduced":["0"],"last_affected":[],"package":"isolated-vm","purl":"pkg:npm/isolated-vm","source":"GHSA-2jjq-x548-rhpv"}],"prev":{"headline":"Mail settings' command parameter injection in mybb","id":"CVE-2022-39265"},"products":["isolated-vm"],"published":"2022-09-29","related":[{"cvss_score":8,"headline":"Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate","id":"CVE-2021-21413","kev_date_added":null,"published":"2021-03-30"}],"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":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["laverdet"]},"summary":"Attackers can bypass the sandbox and execute arbitrary code in the Node.js process by providing malicious cached data to the isolated-vm library.","url":"https://insights.sbomify.com/CVE-2022-39266/"}