# CVE-2026-53553: Goploy: Arbitrary File Read via Path Traversal in /deploy/fileDiff allows Remote Server Compromise

> Attackers can read arbitrary files via path traversal in Goploy, potentially leading to remote server compromise.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026

## What is CVE-2026-53553?

CVE-2026-53553 is a high-severity path traversal vulnerability in zhenorzz goploy, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Goploy is an open-source automation deployment system. Prior to version 1.18.0, a severe path traversal vulnerability exists in its backend API endpoints, specifically /deploy/fileDiff (File Compare), when handling file paths provided by the client. This issue has been patched in version 1.18.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-53553?


## How do I fix CVE-2026-53553?

Upgrade to a fixed version.

## Is CVE-2026-53553 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53553 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53553 and fix it if it is affected.

What it is: CVE-2026-53553 is a high-severity path traversal vulnerability in zhenorzz goploy, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53553 exists.

Affected product: zhenorzz goploy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53553/ (Markdown: https://insights.sbomify.com/CVE-2026-53553/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53553
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53553
- OSV: https://osv.dev/vulnerability/CVE-2026-53553

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53553/
Summaries are generated and may contain mistakes; the official description above is the record.