# CVE-2022-39266: isolated-vm has vulnerable CachedDataOptions in API

> Attackers can bypass the sandbox and execute arbitrary code in the Node.js process by providing malicious cached data to the isolated-vm library.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-2jjq-x548-rhpv

## What is CVE-2022-39266?

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.

### Official 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.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-39266?

2 open source packages ship an affected version, including isolated-vm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `isolated-vm` | npm | All versions | 4.3.7 |
| `isolated-vm` | npm | All versions | 4.3.7 |

Products: Isolated-Vm Project Isolated-Vm.

## How do I fix CVE-2022-39266?

Upgrade isolated-vm to 4.3.7 or later.

## Is CVE-2022-39266 being exploited?

There is no known exploitation of CVE-2022-39266 in the wild and no public exploit code.

## Other vulnerabilities in laverdet isolated-vm

- [CVE-2021-21413](https://insights.sbomify.com/CVE-2021-21413/): Misuse of `Reference` and other transferable APIs may lead to access to nodejs isolate (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39266 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2022-39266 in the wild and no public exploit code.

Affected packages and fixed versions:
- isolated-vm (npm): affected all versions; fixed in 4.3.7
- isolated-vm (npm): affected all versions; fixed in 4.3.7

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39266/ (Markdown: https://insights.sbomify.com/CVE-2022-39266/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39266
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39266
- OSV: https://osv.dev/vulnerability/CVE-2022-39266

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39266/
Summaries are generated and may contain mistakes; the official description above is the record.