Cross-namespace file access and RCE via unchecked IDs
Published Aug 31, 2026 · Updated Sep 1, 2026
Incorrect authorization in Goploy 1.17.5 and earlier allows remote authenticated users to alter cross-namespace files and projects. The project handlers trust body-supplied project and project-file row IDs, while model lookups filter only by row ID rather than caller namespace. Manager or FileSync/EditProject permission enables cross-tenant reads, writes, deletions, and git-URL replacement that executes attacker code on deployment.
Summary
What happened
Incorrect authorization in Goploy 1.17.5 and earlier allows remote authenticated users to alter cross-namespace files and projects. The project handlers trust body-supplied project and project-file row IDs, while model lookups filter only by row ID rather than caller namespace. Manager or FileSync/EditProject permission enables cross-tenant reads, writes, deletions, and git-URL replacement that executes attacker code on deployment.
The record
- CVE
- CVE-2026-53552
- Published
- Aug 31, 2026
- Updated
- Sep 1, 2026
- Vendor
- zhenorzz
- Product
- Goploy
- Classifications
- CWE-863, CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.17.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory cross-namespace proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo