EUVD-2026-45028Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
PR:H reflects mandatory WRITE_PROJECT_RELEASE permission; S:U because writes remain within the process user's existing OS authorization boundary; C:N as no read primitive exists.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Path traversal in Activepieces Enterprise Edition git-sync prior to 0.82.0 allows an authenticated project administrator to overwrite arbitrary files on the host filesystem, with potential impact ranging from data tampering and denial of service to remote code execution. Two distinct weaknesses compound each other: Git's symbolic-link handling was not disabled during repository cloning, and user-supplied identifiers - repository slug and the externalId fields for flows, tables, and connections - were concatenated into filesystem paths without sanitization of directory-traversal sequences. No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog, but the patch commit makes exploitation paths derivable by any skilled attacker reviewing the open-source diff.
Technical ContextAI
The vulnerable code resides in the Enterprise Edition git-sync subsystem, specifically packages/server/api/src/app/ee/projects/project-release/git-sync/git-helper.ts and git-sync-helper.ts. The feature clones a user-configured remote Git repository into a server-side temporary directory and then writes serialized flow, table, and connection state as JSON files before pushing back. CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) manifests via two separate code paths: (1) Git's core.symlinks configuration was left at its default enabled value, so a malicious repository could embed symlinks that redirect server-side file writes to arbitrary host paths outside the cloned workspace; (2) gitRepo.slug and externalId-derived filenames were passed directly to path.join() without stripping ../ sequences, allowing traversal out of the intended project subdirectory. The fix, visible in commit 01bd4ef, adds core.symlinks=false and protocol.file.allow=never to the Git configuration, introduces assertSafeSlug() and resolveSafeJsonPath() functions enforcing the pattern ^[A-Za-z0-9._-]{1,128}$, and adds an assertPathInside() boundary check at every path construction site.
RemediationAI
Upgrade to Activepieces version 0.82.0 or later, available at https://github.com/activepieces/activepieces/releases/tag/0.82.0; this is the only fully effective fix. If immediate upgrade is not feasible, restrict the WRITE_PROJECT_RELEASE permission to the minimum required set of trusted users, as this permission is the sole authentication gate for the attack - removing it from untrusted accounts eliminates the exposure for those accounts. As an additional compensating control, run the Activepieces server process under a dedicated low-privilege OS account with write access scoped to only the application's own data directories, limiting the blast radius of any arbitrary write to non-critical paths. Disabling the git-sync feature entirely is a viable workaround for organizations that do not use it. Note: restricting network access to the Activepieces API does not mitigate this vulnerability because exploitation requires an authenticated session, not unauthenticated network access.
Same weakness CWE-22 – Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today