# CVE-2026-101169: Deserialization in Octopus Server

> Authenticated users with edit permissions can execute arbitrary code via insecure deserialization of crafted JSON in 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:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-cj2p-238w-jrf5

## What is CVE-2026-101169?

CVE-2026-101169 is a high-severity unsafe deserialization vulnerability in Octopus Server, published on 29 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, an authenticated user with permissions to edit an Environment or Project can set specifically crafted JSON content for the object. Insecure deserialization of this content allows the user to execute arbitrary code in the Octopus Server process.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-101169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101169 is a high-severity unsafe deserialization vulnerability in Octopus Server, published on 29 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-101169 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-101169/ (Markdown: https://insights.sbomify.com/CVE-2026-101169/index.md)
```

## Sources

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

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