# CVE-2026-53535: Activepieces: Arbitrary file write in git-sync via path traversal and symlinks

> An attacker with git-sync permissions can overwrite arbitrary files via path traversal and symlinks, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-qqcr-rg2x-97mm

## What is CVE-2026-53535?

CVE-2026-53535 is a medium-severity path traversal vulnerability in activepieces, published on 16 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Activepieces is an open source AI workflow automation platform. Prior to 0.82.0, the git-sync feature clones a user-configured Git repository into a temporary directory on the server and then writes flow, table, and connection state into it before pushing back, and two separate weaknesses allowed those writes to escape the intended workspace and land on arbitrary paths on the host filesystem: Git's symbolic-link handling was not disabled on the clone, so an attacker who controlled the remote repository could include symlinks that redirected the writes, and several user-supplied identifiers used to build on-disk paths (the repository slug and the externalId of tables, flows, and connections) were not validated against directory-traversal sequences such as ../. On a self-hosted Enterprise Edition deployment, a user authorized to configure or push to a git-sync repository (holding the WRITE_PROJECT_RELEASE permission) could cause the server to overwrite files anywhere the Activepieces process user can write, which depending on host layout can be leveraged for tampering, denial of service, or remote code execution. This issue is fixed in version 0.82.0.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-53535 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53535 is a medium-severity path traversal vulnerability in activepieces, published on 16 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53535 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-53535/ (Markdown: https://insights.sbomify.com/CVE-2026-53535/index.md)
```

## Sources

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

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