Is CVE-2026-101169 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-101169 being exploited in the wild.

How severe is CVE-2026-101169?

Informational severity, published 29 September 2026.

Which products and versions are affected?

Octopus Deploy Octopus Server All 2019.4.x through 2025.x; 2026.1.x before 2026.1.11781; 2026.2.x before 2026.2.13441; 2026.3.x before 2026.3.15829; 2026.4.x before 2026.4.1619 (Cloud only).

Is there a fix for CVE-2026-101169?

A patch was published on 2026-09-14: Patch release date Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-101169 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-101169?

Check whether you run Octopus Deploy Octopus Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-101169: Octopus Server insecure deserialization in JSON

CVE-2026-101169 · Severity: info · Published 2026-09-29

Octopus Server is a deployment automation platform used by organizations to manage releases across their infrastructure. An authenticated user with edit permissions on Environments or Projects can inject malicious JSON that the server deserializes unsafely, allowing them to execute arbitrary code on the Octopus Server itself. This gives attackers a foothold to compromise the entire deployment pipeline and access sensitive credentials and configurations.

Technologies: Octopus Deploy Octopus Server. Vendors: Octopus Deploy.

Quick answers

Is CVE-2026-101169 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-101169 being exploited in the wild.
How severe is CVE-2026-101169?: Informational severity, published 29 September 2026.
Which products and versions are affected?: Octopus Deploy Octopus Server All 2019.4.x through 2025.x; 2026.1.x before 2026.1.11781; 2026.2.x before 2026.2.13441; 2026.3.x before 2026.3.15829; 2026.4.x before 2026.4.1619 (Cloud only).
Is there a fix for CVE-2026-101169?: A patch was published on 2026-09-14: Patch release date Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-101169 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-101169?: Check whether you run Octopus Deploy Octopus Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is insecure deserialization of untrusted JSON data in Octopus Server when processing Environment or Project object definitions. An authenticated attacker with edit permissions can craft JSON payloads that execute arbitrary code during deserialization within the Octopus Server process. The vendor has released patched versions across multiple feature branches and recommends immediate upgrade to at least 2026.1.11781, 2026.2.13441, or 2026.3.15829.

Affected products

Octopus Deploy Octopus Server All 2019.4.x through 2025.x; 2026.1.x before 2026.1.11781; 2026.2.x before 2026.2.13441; 2026.3.x before 2026.3.15829; 2026.4.x before 2026.4.1619 (Cloud only)

Timeline

2026-09-04: disclosed: Discovery date per advisory
2026-09-14: patched: Patch release date
2026-09-29: advisory: Advisory published

References

https://advisories.octopus.com/post/2026/sa2026-10

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.