CVE
Octopus Server privilege escalation in team-scoped roles
Affects Octopus Server 2019.0.0 up to 2026.2.13526, and 2026.3.0 up to 2026.3.15909, for users who hold permission to edit team scoped roles. Fixed in 2026.2.13526 and 2026.3.15909.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.13526, 2026.3.15909
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. A user holds permission to edit team scoped roles. Octopus Server runs an affected version: any 2019.x through 2025.x, or 2026.x before 2026.2.13526, or 2026.3 before 2026.3.15909.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In Octopus Server from Octopus Deploy, a user who already has permission to edit team-scoped roles can escalate their privileges to deploy to projects and environments they are not authorized to access. The attack is carried out over the network and requires the attacker to be logged in with high privileges.
Original description
In affected versions of Octopus Server, a user with permission to edit team scoped roles could escalate their privileges to deploy to projects and environments that they were not authorised to so.
Who should check
Teams running self-hosted Octopus Server 2019.x through 2026.x before the fixed builds 2026.2.13526 or 2026.3.15909. Octopus Cloud is already patched.
“All 2019.x, 2020.x, 2021.x, 2022.x, 2023.x 2024.x and 2025.x versions”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
A user holds permission to edit team scoped roles. Octopus Server runs an affected version: any 2019.x through 2025.x, or 2026.x before 2026.2.13526, or 2026.3 before 2026.3.15909.Upgrade to a fixed version: 2026.2.13526, 2026.3.15909.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-116288 (In affected versions of Octopus Server, a user with permission to edit team scoped roles could escalate their privileges to deploy to…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-116288 (entry last updated 2026-11-16):
Affected:
- Octopus Deploy Octopus Server: from 2019.0.0, fixed in 2026.2.13526; from 2026.3.0, fixed in 2026.3.15909
Fixed versions: 2026.2.13526, 2026.3.15909.
Conditions (all must be true for the bug to be hit):
- A user holds permission to edit team scoped roles. (source: https://advisories.octopus.com/post/2026/sa2026-28/)
- Octopus Server runs an affected version: any 2019.x through 2025.x, or 2026.x before 2026.2.13526, or 2026.3 before 2026.3.15909. (source: https://advisories.octopus.com/post/2026/sa2026-28/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-116288 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116288 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisories.octopus.com/post/2026/sa2026-28
- https://advisories.octopus.com/post/2026/sa2026-28/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-116288
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116288"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Octopus Deploy Octopus Server
From 2019.0.0 · fixed in 2026.2.13526; From 2026.3.0 · fixed in 2026.3.15909
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116288
Is CVE-2026-116288 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user with permission to edit team scoped roles can escalate their privileges and deploy to projects and environments they were not authorised to access.Source: advisories.octopus.com
Which versions are affected by CVE-2026-116288?
Octopus Server: from 2019.0.0 before 2026.2.13526; from 2026.3.0 before 2026.3.15909.Source: cve.now feed data
Am I affected, and how do I check?
Octopus Server 2019.x through 2025.x, 2026.x before 2026.2.13526, and 2026.3 before 2026.3.15909 are affected. Check the installed Octopus Server version against these ranges, and check whether any users hold permission to edit team scoped roles.Source: advisories.octopus.com
How do I fix CVE-2026-116288?
Upgrade to 2026.2.13526 on the 2026.2 line or to 2026.3.15909 on the 2026.3 line.Source: advisories.octopus.com