Privilege Escalation via Unrestricted Role Modification in Octopus Server
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Octopus Deploy | Octopus Server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Octopus | Octopus Server |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.295% probability within 30 days)
| Link | Providers |
|---|---|
| https://advisories.octopus.com/post/2026/sa2026-11 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Octopus
Octopus octopus Server |
|
| Vendors & Products |
Octopus
Octopus octopus Server |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Privilege Escalation via Unrestricted Role Modification in Octopus Server |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In affected versions of Octopus Server, an authenticated user with permission to modify roles could bypass the protections preventing access abuse resulting in privilege escalation. It was possible for the built-in role to be weakened and the attacker's account added to a privileged team. This was achievable due to improper validation of unsafe equivalence in inputs. | |
| Weaknesses | CWE-1289 | |
| References |
| |
| Metrics |
cvssV4_0
|