CVE-2026-116870: Octopus Deploy Octopus Server vulnerability

Published Oct 27, 2026
·
Updated

In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently. This could result in a token issued from a suitably configured non legitimate issuer being accepted as a token belonging to a service account from a legitimate trusted issuer. Exploitation requires a service account with at least one OIDC identity configured. An attacker would also need to know or guess some details of that identity in order to be in a position to attempt exploitation.

Affected Software

1 affected component
Octopus Deploy Octopus Server

Event History

Oct 27, 2026
CVE Published
via MITRE·10:28 AM
Data Sourced
via MITRE·10:28 AM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Exposure requires a service account that has at least one OIDC identity configured. Deployments without such a service account are not described as exploitable by the available information.

2

What does an attacker need to attempt exploitation?

An attacker needs a suitably configured non-legitimate token issuer and must know or guess details of an OIDC identity configured on a service account. The issue concerns that issuer's token being accepted as belonging to a service account associated with a legitimate trusted issuer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203