Is CVE-2026-116835 exploited in the wild?

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

How severe is CVE-2026-116835?

Informational severity, published 12 November 2026.

Which products and versions are affected?

Octopus Deploy Octopus Server 2025.3.x after 2025.3.11571, 2025.4.x, 2026.1.x, 2026.2.x before 2026.2.13503, 2026.3.x before 2026.3.15894.

Is there a fix for CVE-2026-116835?

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

How is CVE-2026-116835 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-116835?

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-116835: Octopus Server OIDC claim validation bypass

CVE-2026-116835 · Severity: info · Published 2026-11-12

Octopus Server is a deployment automation platform that manages application releases and integrations with cloud providers. An authenticated user with account edit permissions can manipulate OIDC authentication tokens to impersonate other projects, potentially gaining unauthorized access to external systems like cloud platforms or other Octopus instances that trust those project identities.

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

Quick answers

Is CVE-2026-116835 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116835 being exploited in the wild.
How severe is CVE-2026-116835?: Informational severity, published 12 November 2026.
Which products and versions are affected?: Octopus Deploy Octopus Server 2025.3.x after 2025.3.11571, 2025.4.x, 2026.1.x, 2026.2.x before 2026.2.13503, 2026.3.x before 2026.3.15894.
Is there a fix for CVE-2026-116835?: Yes: fixed in Octopus Server 2026.2.13503, 2026.3.15894. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116835 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-116835?: 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.2.13503, 2026.3.15894

Technical details

The vulnerability stems from insufficient validation of custom claims in OIDC accounts. An attacker with permission to edit accounts can craft signed OIDC tokens with spoofed subject and project claims, enabling cross-project impersonation. This requires authenticated access to account management functions but allows arbitrary project identity assumption.

Affected products

Octopus Deploy Octopus Server 2025.3.x after 2025.3.11571, 2025.4.x, 2026.1.x, 2026.2.x before 2026.2.13503, 2026.3.x before 2026.3.15894

Timeline

2026-10-06: disclosed
2026-10-08: patched
2026-11-12: advisory

References

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

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