Read the docs

Insufficient authorization on Octopus Server scheduled project triggers

Priority LOW 21CWE-863Published · Updated

Key facts

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

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

Summary

Octopus Deploy Octopus Server from 2018.4.0 before 2026.2.13558 and from 2026.3.0 before 2026.3.16030 has insufficient authorization checks on scheduled project triggers (CWE-863). A user permitted to deploy existing releases but not to create new ones can configure a trigger that creates and deploys new releases without the required permission being assigned. The resulting audit events are attributed to the system rather than to the user who configured the trigger. An authenticated remote attacker with low privileges can exploit this with no user interaction, which affects integrity.

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

Description from the CNA

In affected versions of Octopus Server, insufficient authorization checks on scheduled project triggers allowed users who were permitted to deploy existing releases, but not to create new ones, to configure a trigger that could result in new releases being created and deployed without the required permission being assigned. The resulting audit events were attributed to the system rather than to the user who configured the trigger.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
Fix Fixed Octopus Server (Octopus Deploy): 2026.2.13558, 2026.3.16030

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Octopus DeployOctopus Server2018.4.0 to before 2026.2.13558; 2026.3.0 to before 2026.3.160302026.2.13558, 2026.3.16030Patch availableCNA
  • Octopus Server VendorOctopus Deploy Affected 2018.4.0 to before 2026.2.13558; 2026.3.0 to before 2026.3.16030 Fixed in 2026.2.13558, 2026.3.16030 Patch available CNA

Remediation

Upgrade Octopus Server to version 2026.2.13558 or 2026.3.16030, or a later release of the same branch. The sources do not list a vendor advisory identifier for this fix.

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

  • Fix · CNA Octopus Server (Octopus Deploy) Fixed in 2026.2.13558, 2026.3.16030

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Octopus Server 2026.2.13558, 2026.3.16030

    2 records Highest priority Priority MEDIUM 1 MEDIUM, 1 LOW

    Other records, highest priority first

    • TI-2026-92083 Path traversal in Octopus Server lets scoped users read and delete filesPriority MEDIUM 42

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-124629
  2. 2026-11-16 Alias added: GHSA-87pv-728w-pg58
  3. 2026-11-16 CISA SSVC decision points changed

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