Security readout for executives and security teams
Plain-English summary
A user trusted to manage projects in one Goploy namespace can reportedly alter projects belonging to other namespaces. This can expose, modify, or delete deployment files and redirect a project's Git source. A later deployment may execute attacker-controlled code, creating organization-wide compromise risk.
Executive priority
Treat this as an immediate containment and investigation priority. Limit privileged access, verify Git remotes, and scrutinize recent deployments. Because no public patch was known at publication, leadership should consider temporarily suspending affected deployment workflows where access cannot be tightly controlled.
Technical view
Goploy 1.17.5 and earlier accepts project or project-file row IDs from request bodies without verifying namespace ownership. Several project handlers and their underlying data queries authorize by permission but retrieve records only by row ID. Cross-namespace file access and Git remote modification can lead to code execution during a subsequent deployment.
Likely exposure
Goploy installations running version 1.17.5 or earlier are affected when a user has the manager role, FileSync permission, or EditProject permission. Multi-namespace installations and environments where Goploy can deploy into sensitive systems face the greatest risk. Publicly reachable management interfaces may increase opportunity, but are not required by the described flaw.
Exploitation context
The vulnerability requires an authenticated low-privileged user with specified project-management permissions. Exploitation can cross namespace boundaries without user interaction. Code execution is not immediate; the described Git remote modification becomes effective on the affected project's next deployment. The supplied sources do not establish active exploitation, and the CVE is not listed as KEV.
Researcher notes
The core issues are cross-tenant authorization failures classified as CWE-639 and CWE-863. Project.AddFile, EditFile, RemoveFile, and Edit reportedly trust body-supplied row IDs, while ProjectFile.GetData and Project.GetData filter only by ID. The scope-changing impact and subsequent deployment-triggered execution support the supplied CVSS 3.1 score of 9.6.
Mitigation direction
- Check the vendor advisory frequently for an official patch or updated release.
- Temporarily remove FileSync and EditProject permissions from nonessential users.
- Restrict Goploy management access to trusted administrators and controlled networks.
- Pause deployments for potentially affected projects until Git remotes and files are verified.
- Review and rotate credentials accessible to Goploy if compromise indicators are found.
Validation and detection
- Inventory all Goploy installations and confirm their exact versions.
- Identify users and roles holding FileSync or EditProject permissions.
- Review project and project-file changes for unexpected cross-namespace activity.
- Verify every project's Git remote URL against an approved repository inventory.
- Examine deployments after suspicious configuration changes for unauthorized code or artifacts.
- Confirm namespace ownership checks after applying any future vendor fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53552 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/zhenorzz/goploy/security/advisories/GHSA-26rh-24rg-j3vvCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.