# CVE-2026-73083: Activepieces: V8 Isolate Sandbox Bypass via importFresh Module Loading

> Authenticated users can bypass the V8 sandbox in Activepieces to execute arbitrary code and access sensitive environment secrets.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-gr3h-c2j7-r52g

## What is CVE-2026-73083?

CVE-2026-73083 is a high-severity vulnerability in activepieces, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Activepieces is an open source AI workflow automation platform. Prior to 0.80.0, in SANDBOX_CODE_ONLY mode, the engine loads the compiled user module with importFresh(), a wrapper around Node.js require(), before the V8 isolate is applied. Top-level module code can therefore call require('child_process'), access fs, and use other Node.js APIs in the host engine process outside the sandbox. An authenticated user who can create a Code step can read environment secrets including AP_ENCRYPTION_KEY and AP_JWT_SECRET, read or write files, and reach internal services. This issue is fixed in version 0.80.0.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2026-73083?


## How do I fix CVE-2026-73083?

No fix has been published for CVE-2026-73083 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73083 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73083 and fix it if it is affected.

What it is: CVE-2026-73083 is a high-severity vulnerability in activepieces, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73083 in the wild and no public exploit code.

Affected product: activepieces. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-73083/ (Markdown: https://insights.sbomify.com/CVE-2026-73083/index.md)
```

## Sources

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

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