Is CVE-2026-116870 exploited in the wild?

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

How severe is CVE-2026-116870?

Informational severity, published 27 October 2026.

Which products and versions are affected?

Octopus Deploy Octopus Server 2024.1.11866 through 2024.x, all 2025.x, 2026.1.x before 2026.1.11781, 2026.2.x before 2026.2.13438, 2026.3.x before 2026.3.15816.

Is there a fix for CVE-2026-116870?

Yes: fixed in Octopus Server 2026.1.11781, 2026.2.13438, 2026.3.15816. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-116870 attacked?

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

Am I affected by CVE-2026-116870?

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-116870: Octopus Server OIDC token issuer validation bypass

CVE-2026-116870 · Severity: info · Published 2026-10-27

Octopus Server is deployment automation software used to manage application releases across infrastructure. A flaw in how it validates OIDC (OpenID Connect) tokens allows an attacker to forge tokens that impersonate service accounts, potentially gaining unauthorized deployment capabilities. Successful exploitation requires the attacker to have detailed knowledge of a legitimate service account's OIDC identity and to control a non-legitimate issuer.

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

Quick answers

Is CVE-2026-116870 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116870 being exploited in the wild.
How severe is CVE-2026-116870?: Informational severity, published 27 October 2026.
Which products and versions are affected?: Octopus Deploy Octopus Server 2024.1.11866 through 2024.x, all 2025.x, 2026.1.x before 2026.1.11781, 2026.2.x before 2026.2.13438, 2026.3.x before 2026.3.15816.
Is there a fix for CVE-2026-116870?: Yes: fixed in Octopus Server 2026.1.11781, 2026.2.13438, 2026.3.15816. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116870 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-116870?: 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.

How to fix

Fixed in: Octopus Server 2026.1.11781, 2026.2.13438, 2026.3.15816

Technical details

The vulnerability stems from inconsistent OIDC token issuer validation in Octopus Server, allowing a token from an attacker-controlled issuer to be accepted as originating from a legitimate trusted issuer. An attacker must know or guess details of an existing service account's OIDC identity configuration to exploit this. The flaw enables token forgery and service account impersonation when OIDC identities are configured on service accounts.

Affected products

Octopus Deploy Octopus Server 2024.1.11866 through 2024.x, all 2025.x, 2026.1.x before 2026.1.11781, 2026.2.x before 2026.2.13438, 2026.3.x before 2026.3.15816

Timeline

2026-09-09: disclosed: Discovery date
2026-09-14: patched: Patch release date
2026-10-27: advisory: Public advisory release

References

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

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