Read the docs

Improper claim validation in Octopus Server lets users impersonate projects

Priority LOW 37CWE-915Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Tampering
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-915.

Summary

Octopus Server versions from 2025.3.11571 before 2026.2.13503 and from 2026.3.0 before 2026.3.15894 do not sufficiently validate custom claims on OIDC accounts. A user with permission to edit accounts can make the server issue signed OIDC tokens that impersonate a different project, which is a case of improperly controlled modification of dynamically determined object attributes (CWE-915). An authenticated attacker with low privileges can exploit this over the network without user interaction. The forged tokens could grant access to external systems, such as cloud providers or other Octopus instances, that trust that project's identity.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the CNA

In affected versions of Octopus Server, insufficient validation of custom claims on OIDC accounts allowed a user with permission to edit accounts to cause Octopus Server to issue signed OIDC tokens that impersonate a different project. This could grant access to external systems, such as cloud providers or other Octopus instances, that trust that project's identity.

Why it matters now

EPSS 0.00244 15th percentileScored 2026-11-16
Fix Fixed Octopus Server (Octopus Deploy): 2026.2.13503, 2026.3.15894

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Octopus DeployOctopus Server2025.3.11571 to before 2026.2.13503; 2026.3.0 to before 2026.3.158942026.2.13503, 2026.3.15894Patch availableCNA
  • Octopus Server VendorOctopus Deploy Affected 2025.3.11571 to before 2026.2.13503; 2026.3.0 to before 2026.3.15894 Fixed in 2026.2.13503, 2026.3.15894 Patch available CNA

Remediation

Upgrade Octopus Server to 2026.2.13503 or 2026.3.15894. The sources list no advisory identifier for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · CNA Octopus Server (Octopus Deploy) Fixed in 2026.2.13503, 2026.3.15894

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-116835
  2. 2026-11-12 Alias added: GHSA-x27r-mfxr-pcpj

References

  • TI-2018-13353 In Octopus Deploy 2018.8.0 through 2018.9.x before 2018.9.1, an authenticated user with… CVSS 3.0HIGH 8.8
  • TI-2022-02375 Improper authentication in Octopus Server CVSS 3.1CRITICAL 9.8
  • TI-2022-02579 Insufficient session expiration in Octopus Server CVSS 3.1CRITICAL 9.1
  • TI-2021-11816 Deserialization of untrusted data in Octopus Deploy Halibut CVSS 3.1CRITICAL 9.8
  • TI-2018-08066 In Octopus Deploy 2018.4.4 through 2018.5.1, Octopus variables that are sourced from the… CVSS 3.0CRITICAL 9.8
  • TI-2022-02575 In affected versions of Octopus Deploy it is possible to bypass rate limiting on login using null bytes. CVSS 3.1CRITICAL 9.8
See all 127 →

Sources