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.
Published: 2026-10-27
Score: 8.7 High
EPSS: n/a
KEV: No
Impact: Authorization Bypass via Unauthorized Token Acceptance
Action: Immediate patch
AI Analysis

Impact

Octopus Deploy's Octopus Server inconsistently validates the issuer claim of OpenID Connect tokens, allowing an attacker to supply a token issued by a non‑legitimate but properly configured issuer that is accepted as belonging to a legitimate service account. This flaw represents an improper authentication weakness (CWE-1289) that can enable unauthorized impersonation and potentially grant an attacker the permissions of the compromised service account.

Affected Systems

All affected Octopus Server versions released by Octopus Deploy, as identified in the advisory. No specific patch version is listed, so all versions prior to the release of the fix remain vulnerable.

Risk and Exploitability

The CVSS score of 8.7 classifies this vulnerability as high severity. EPSS data is not available, and it is not listed in the CISA KEV catalog. Exploitation requires an attacker to have a service account with at least one OIDC identity configured and to know or guess some details of that identity, suggesting that passive information gathering or social engineering may be prerequisites. Once exploited, the attacker could impersonate the service account and gain whatever access that account provides, potentially compromising internal workflows and automation tooling.

Generated by OpenCVE AI on October 27, 2026 at 11:20 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Octopus Server to the latest version where the OIDC issuer validation fix is released
  • Restrict OIDC issuer configuration so that only trusted issuers are allowed and remove any unnecessary or unknown issuers from service account identities
  • Review and audit existing service account OIDC identities, eliminating any configuration that could expose the system to issuer spoofing
  • Enable detailed auditing and monitoring for OIDC authentication events to detect anomalous token usage

Generated by OpenCVE AI on October 27, 2026 at 11:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 27 Oct 2026 11:45:00 +0000

Type Values Removed Values Added
Title Inconsistent OIDC Token Issuer Validation Allows Unauthorized Token Acceptance

Tue, 27 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
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.
Weaknesses CWE-1289
References
Metrics cvssV4_0

{'score': 8.7, '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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Octopus

Published:

Updated: 2026-10-27T10:28:11.007Z

Reserved: 2026-10-27T00:58:00.462Z

Link: CVE-2026-116870

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-27T11:17:28.610

Modified: 2026-10-27T11:17:28.610

Link: CVE-2026-116870

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-27T11:30:13Z

Weaknesses
  • CWE-1289

    Improper Validation of Unsafe Equivalence in Input