Quick answers
- Is CVE-2026-12813 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12813 being exploited in the wild.
- How severe is CVE-2026-12813?
- Medium severity, with a CVSS score of 6.3, published 21 June 2026.
- Which products and versions are affected?
- Activepieces up to 0.83.0.
- Is there a fix for CVE-2026-12813?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-12813 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-12813?
- 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 Server-Side Request Forgery (SSRF) vulnerability exists in Activepieces versions up to 0.83.0 within the 'handleUrlFile' function located in 'packages/server/engine/src/lib/variables/processors/file.ts'. The vulnerability stems from the 'Property.File' processor using a raw global 'fetch()' call on user-provided URL values without applying the engine's SSRF protection guards. A remote attacker with low privileges (authenticated workflow user) can provide a malicious URL to force the worker context to fetch data from loopback addresses, private networks, or cloud metadata endpoints. As of the advisory date, the vendor has not responded to the disclosure, and a public exploit exists.
Affected products
- activepieces activepieces up to 0.83.0
Timeline
- 2026-06-21: disclosed: Public disclosure of the vulnerability and exploit.
- 2026-06-21: advisory: CVE-2026-12813 published.