In affected versions of Octopus Server, insufficient authorization checks on scheduled project triggers allowed users
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2026.3.16030 or 2026.2.13558 when convenient.
Data as of 16 Nov 2026, 13:36 UTC
Thin evidence
One scorer or none| CNA (Octopus) | CVSS 4.0 | 5.3 |
|---|
- Patch
- Available – fixed in 2026.3.16030, 2026.2.13558
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade Octopus Server to 2026.3.16030 or 2026.2.13558.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Octopus DeployOctopus Server | Affected
| Fixed in
|
| Octopus DeployOctopus Server | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict permissions carefully and monitor scheduled triggers for unauthorized configurations.
Description
A vulnerability in certain versions of Octopus Server allows users with deployment permissions but without release creation rights to configure scheduled project triggers that create and deploy new releases without proper authorization. Audit logs incorrectly attribute these actions to the system instead of the responsible user.