Goploy: Cross-namespace IDOR and RCE via body-supplied row id in project and project_file handlers
CVE-2026-53552GHSA-26rh-24rg-j3vv
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zhenorzz/goploy 1.18.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 1.18.0
- Fixed in
- 1.18.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-26rh-24rg-j3vv lists affected ranges: Go github.com/zhenorzz/goploy >=0 <=1.17.5
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-26rh-24rg-j3vv lists affected ranges: Go github.com/zhenorzz/goploy >=0 <1.18.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
- EPSS
- CVE-2026-53552: 0.35% estimated exploitation activity in the next 30 days; percentile 28.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary `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.
Affected `zhenorzz/goploy` `develop` HEAD as of 2026-05-27. Verified against the `zhenorzz/goploy:1.17.5` Docker image…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from osv record GHSA-26rh-24rg-j3vv
- Revision 2 · amended ·
Amended from ghsa record GHSA-26rh-24rg-j3vv
- Revision 1 · created ·
Published from ghsa record GHSA-26rh-24rg-j3vv
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-53552 Advisory: Goploy: Cross-namespace IDOR and RCE via body-supplied row id in project and project_file handlers IDs: CVE-2026-53552, GHSA-26rh-24rg-j3vv Record: https://patchnext.com/advisories/cve-2026-53552 (revision 3, source checked 28 Oct 2026, 06:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/zhenorzz/goploy 1.18.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/zhenorzz/goploy: affected < 1.18.0; fixed in 1.18.0 ## Suggested inspection (read-only) - Go github.com/zhenorzz/goploy: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/zhenorzz/goploy. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-26rh-24rg-j3vv (GitHub-reviewed advisory GHSA-26rh-24rg-j3vv lists affected ranges: Go github.com/zhenorzz/goploy >=0 <=1.17.5) - Verified: https://osv.dev/vulnerability/GHSA-26rh-24rg-j3vv (OSV record GHSA-26rh-24rg-j3vv lists affected ranges: Go github.com/zhenorzz/goploy >=0 <1.18.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…