Octopus Server Fixes Unauthorized Release Creation by Scheduled Triggers
Quick Answer
Upgrade affected self-hosted Octopus Server installations and review scheduled triggers that could create releases without ReleaseCreate permission.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory self-hosted Octopus Server versions, scheduled project triggers, release-creation permissions and users who can configure deployment schedules. Review users who may deploy existing releases but lack ReleaseCreate. Compare scheduled trigger configuration with change records and audit events attributed to the system. Use the fixed version for the deployed release line, or upgrade to the vendor-recommended 2026.3.16117 release. Octopus Cloud instances have already been updated and require no further customer action for this advisory. Test a deployment-only role against scheduled release creation and confirm permitted schedules still run. Retain role exports, trigger configuration, audit records and upgrade evidence.
Last verified: 2026-11-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Self-hosted Octopus Server on Linux and Microsoft Windows |
|---|---|
| Advisory | SA2026-25 |
| CVE | CVE-2026-124629 |
| Authoritative release date | 2026-11-16T06:47:48Z — official advisory RSS publication time converted from UTC+10; patch released October 28, 2026. |
| Authority revision date | No separate material advisory revision is confirmed. |
| Affected versions | 2018.x after 2018.4.0; all 2019.x–2025.x and 2026.1.x; 2026.2.x before 2026.2.13558 and 2026.3.x before 2026.3.16030. |
| Fixed version | Octopus Server 2026.2.13558 or 2026.3.16030 or an appropriate later supported release |
| CVSS base score | 5.3 (authority-published CVSS; version not specified on the bulletin) |
| CVSS severity | Medium |
| Exploitation status | Octopus Deploy states that its security team is not aware of malicious use of this vulnerability.; no exploitation claim is inferred. |
What Changed
A user permitted to deploy existing releases could configure a scheduled trigger that created and deployed a new release without ReleaseCreate permission. Audit events were attributed to the system rather than the configuring user.
What To Validate Now
- Inventory. Inventory self-hosted Octopus Server versions, scheduled project triggers, release-creation permissions and users who can configure deployment schedules.
- Establish applicability. Review users who may deploy existing releases but lack ReleaseCreate. Compare scheduled trigger configuration with change records and audit events attributed to the system.
- Remediate. Use the fixed version for the deployed release line, or upgrade to the vendor-recommended 2026.3.16117 release. Octopus Cloud instances have already been updated and require no further customer action for this advisory.
- Validate. Test a deployment-only role against scheduled release creation and confirm permitted schedules still run. Retain role exports, trigger configuration, audit records and upgrade evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
The advisory was disclosed November 16; its patch was released October 28, 2026. There is no known mitigation, so a permission review does not replace the upgrade. Plan maintenance with a compatible database backup and verify deployment and integration health afterward.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

