CVE-2026-124629 · Vendor
NO FIX YET
In affected versions of Octopus Server, a user allowed to deploy existing releases could configure a scheduled project trigger that creates and deploys new releases, even though they lack permission to create releases. The audit log records these actions as done by the system rather than by the user who set up the trigger.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running a self-hosted Octopus Server with scheduled project triggers and users who hold deploy-only permissions. The sources do not name affected version ranges, so check the vendor advisory for your version. Instances without scheduled triggers or without restricted deploy-only users are less exposed.
Not affected if no-deploy-only-users, no-scheduled-triggers
Who cares ci-cd, octopus-deploy, self-hosted
Unknown from the sources.
No fix yet, per the sources.
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.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.