Quick answers
- Is CVE-2026-53552 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53552 being exploited in the wild.
- How severe is CVE-2026-53552?
- Critical severity, with a CVSS score of 9.6, published 31 August 2026.
- Which products and versions are affected?
- github.com/zhenorzz/goploy (Go) <= 1.17.5, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.17.5; Zhenorzz Goploy <= 1.17.5.
- Is there a fix for CVE-2026-53552?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-53552 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-53552?
- Check whether you run github.com/zhenorzz/goploy (Go) or Zhenorzz Goploy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the `Project.AddFile`, `Project.EditFile`, `Project.RemoveFile`, and `Project.Edit` handlers within `cmd/server/api/project/handler.go`. These endpoints accept project or file IDs from the JSON request body but fail to verify if the requested ID belongs to the authenticated user's namespace. An attacker with the `manager` role (possessing `FileSync` or `EditProject` permissions) can manipulate files across different namespaces. By using the `Project.Edit` handler to modify a project's git remote URL, an attacker can achieve RCE because the application executes `git remote set-url` on the project's working tree, leading to the execution of arbitrary code during the subsequent deployment process.
Affected products
- zhenorzz Goploy <= 1.17.5
Identifiers
- CVE-2026-53552
- GHSA-26rh-24rg-j3vv
- GO-2026-5936
Timeline
- 2026-05-27: other: Vulnerability verified against develop branch HEAD
- 2026-06-01: disclosed
- 2026-07-07: advisory