Quick answers
- Is CVE-2026-48499 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48499 being exploited in the wild.
- How severe is CVE-2026-48499?
- Informational severity, with a CVSS score of 9.3, published 30 July 2026.
- Which products and versions are affected?
- Activepieces < 0.84.0.
- Is there a fix for CVE-2026-48499?
- A patch was published on 2026-05-21: Security patch committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48499 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-48499?
- Check whether you run Activepieces at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the Code piece sandbox of Activepieces due to unsanitized path segments. An authenticated attacker with permissions to author and execute flows can exploit this to access the read-write cache directory on a shared worker node. This allows the attacker to read cached flow JSON files (potentially containing plaintext secrets) and modify cached code belonging to other tenants. Modified code persists in the cache until eviction, leading to arbitrary code execution in the victim tenant's context during their next flow run. The vulnerability affects versions prior to 0.84.0; V8 isolate execution modes are reportedly not impacted.
Affected products
- activepieces activepieces < 0.84.0
Timeline
- 2026-05-21: patched: Security patch committed to repository
- 2026-05-29: advisory: Release 0.84.0 published
- 2026-07-17: advisory: GitHub Security Advisory GHSA-5h2x-g6m3-grmq published
- 2026-07-30: disclosed: CVE-2026-48499 published to NVD