# CVE-2026-48499: Activepieces: Cross-tenant data exposure and code injection via the Code piece sandbox cache

> Authenticated flow authors can inject code and read data from other tenants via unsanitized path segments in the Code piece sandbox cache.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-5h2x-g6m3-grmq

## What is CVE-2026-48499?

CVE-2026-48499 is a critical code injection vulnerability in activepieces, published on 30 Jul 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.84.0, an unsanitized path segment in the Code piece sandbox can let an authenticated flow author reach read-write cached flow and code files belonging to other tenants on the same worker, exposing embedded data and allowing modified code to execute on a victim tenant's next flow run. This issue is fixed in version 0.84.0.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-668 (Exposure of Resource to Wrong Sphere), CWE-285 (Improper Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-48499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48499 is a critical code injection vulnerability in activepieces, published on 30 Jul 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-48499 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-48499/ (Markdown: https://insights.sbomify.com/CVE-2026-48499/index.md)
```

## Sources

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

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