# CVE-2026-92355: Path traversal in Octopus Server

> An attacker with feed modification permissions can overwrite arbitrary files via path traversal, potentially achieving remote code execution on Octopus Server.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-7f5m-mqg8-7jjg

## What is CVE-2026-92355?

CVE-2026-92355 is a high-severity path traversal vulnerability in Octopus Server, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In affected versions of Octopus Server, a user with permission to modify non built-in external feeds could exploit a path traversal flaw to overwrite arbitrary files on the server, which in some configurations could lead to remote code execution.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-92355 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92355 is a high-severity path traversal vulnerability in Octopus Server, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92355 in the wild and no public exploit code.

Affected product: Octopus Server. 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-92355/ (Markdown: https://insights.sbomify.com/CVE-2026-92355/index.md)
```

## Sources

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

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