# CVE-2026-53552: Goploy: Cross-namespace IDOR and RCE via body-supplied row id in project and project_file handlers

> Authenticated users can manipulate files and git URLs in other namespaces, leading to remote code execution during deployment.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-26rh-24rg-j3vv, GO-2026-5936

## What is CVE-2026-53552?

CVE-2026-53552 is a critical missing authorization vulnerability in zhenorzz goploy, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Goploy is an open-source automation deployment system. In versions 1.17.5 and prior, Project.AddFile, Project.EditFile, Project.RemoveFile, and Project.Edit in cmd/server/api/project/handler.go accept a project or project-file row id from the JSON body and act on it without checking that the project belongs to the caller's namespace. The corresponding model.ProjectFile.GetData and model.Project.GetData queries filter only by row id. A user holding the manager role (or any role that includes the FileSync / EditProject permission) in their own namespace can read, write, or delete files in any project across the install, and can rewrite any project's git remote URL by submitting the foreign id in the body. The git-URL primitive escalates to RCE on the next deploy because Edit runs git remote set-url on the project's working tree. At time of publication, there are no known publicly available patches.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

3 open source packages ship an affected version, including github.com/zhenorzz/goploy.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zhenorzz/goploy` | Go | All versions | None |
| `github.com/zhenorzz/goploy` | Go | All versions | 1.18.0 |
| `github.com/zhenorzz/goploy` | Go | All versions | 1.18.0 |

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

Upgrade github.com/zhenorzz/goploy to 1.18.0 or later.

## Is CVE-2026-53552 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53552 is a critical missing authorization vulnerability in zhenorzz goploy, published on 31 Aug 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-53552 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zhenorzz/goploy (Go): affected all versions; no fix listed
- github.com/zhenorzz/goploy (Go): affected all versions; fixed in 1.18.0
- github.com/zhenorzz/goploy (Go): affected all versions; fixed in 1.18.0

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-53552/ (Markdown: https://insights.sbomify.com/CVE-2026-53552/index.md)
```

## Sources

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

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