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

Advisory record · `GHSA-26rh-24rg-j3vv`

- **Identifiers:** `GHSA-26rh-24rg-j3vv` · `CVE-2026-53552` · `GO-2026-5936`
- **State:** Confirmed
- **Severity:** CVSS 9.6 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 7 Jul 2026
- **Updated:** 27 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Jul 2026, 23:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.6: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/zhenorzz/goploy` (Go): affected `<1.18.0`; fixed in `1.18.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Goploy versions before 1.18.0 let a user with the manager role in their own namespace act on projects and project files in other namespaces. The project and project-file handlers (AddFile, EditFile, RemoveFile, Edit) accept a row id from the request body without checking namespace ownership. An attacker can then read, overwrite, plant, or delete files in other tenants' projects, and rewrite a project's git remote URL, which can lead to remote code execution on the next deploy. Upgrade to goploy 1.18.0 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.6 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-26rh-24rg-j3vv)

## Sources

- [GitHub Advisory Database: GHSA-26rh-24rg-j3vv](https://github.com/advisories/GHSA-26rh-24rg-j3vv)
- [OSV: GHSA-26rh-24rg-j3vv](https://osv.dev/vulnerability/GHSA-26rh-24rg-j3vv)
- <https://github.com/zhenorzz/goploy/security/advisories/GHSA-26rh-24rg-j3vv>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-53552>
- <https://github.com/zhenorzz/goploy/commit/b49eabe903c7d7df1a3763385f5067676da4fdd3>
- <https://github.com/zhenorzz/goploy>
- <https://github.com/zhenorzz/goploy/releases/tag/v1.18.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-26rh-24rg-j3vv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-26rh-24rg-j3vv/>. Everything for agents: <https://agentprime.io/llms.txt>.
