# CVE-2026-114665: Goploy 1.18.0 before 1.18.1 Symlink Following Arbitrary File Read via /deploy/fileDiff and /deploy/fileCompare


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-q5pp-jrgg-4fpm

## What is CVE-2026-114665?

CVE-2026-114665 is a high-severity vulnerability in zhenorzz goploy, published on 22 Oct 2026. 

### Official description

Goploy 1.18.0 before 1.18.1 contains a link following vulnerability in the /deploy/fileDiff and /deploy/fileCompare endpoints that allows authenticated members to read arbitrary files. Attackers with repository write access can commit a symlink pointing outside the project directory to read database configuration and deployment SSH private keys.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

No fix has been published for CVE-2026-114665 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114665 being exploited?

There is no known exploitation of CVE-2026-114665 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114665 is a high-severity vulnerability in zhenorzz goploy, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114665 in the wild and no public exploit code.

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-114665/ (Markdown: https://insights.sbomify.com/CVE-2026-114665/index.md)
```

## Sources

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

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