CVE-2026-93487: Octopus Server (high)

Summary

Octopus Server, from Octopus Deploy, has a flaw in how it checks permissions for users who can create project triggers. A user with low-level login access over the network could run runbooks or create deployments they are not authorised to perform.

Read the original description

In affected versions of Octopus Server, incorrect validation of the permissions assigned to a user that would allow them to create project triggers could result in the user being able to run runbooks or create deployments they were not authorised to perform.

Who should check

Teams running Octopus Server 2019.x through 2026.3.x before the fixed builds, including Linux and Windows installs; Octopus Cloud is already patched.

Read the source excerpt

“All 2020.x, 2021.x, 2022.x, 2023.x 2024.x and 2025.x versions”

advisories.octopus.com

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure8/25Specific setups only, reachable over the network
Reach?/20Unknown. No tracked technology or package matched
Severity7.1/10CVSS 7.1
No patch0/5No signal

What would change the score

Would score about 65 if added to CISA KEV
Would score about 60 if CISA's SSVC rates exploitation active
Would score about 22 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
Running an affected Octopus Server version (2019.x after 2019.11.x, 2020.x through 2025.x, 2026.x before 2026.2.13487, or 2026.3 before 2026.3.15863).
Upgrade to a fixed version: 2026.2.13487, 2026.3.15863.

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-93487 (In affected versions of Octopus Server, incorrect validation of the permissions assigned to a user that would allow them to create project…), 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-93487 (entry last updated 2026-11-11):
Affected:
- Octopus Deploy Octopus Server: from 2019.11.0, fixed in 2026.2.13487; from 2026.3.0, fixed in 2026.3.15863
Fixed versions: 2026.2.13487, 2026.3.15863.
Conditions (all must be true for the bug to be hit):
- Running an affected Octopus Server version (2019.x after 2019.11.x, 2020.x through 2025.x, 2026.x before 2026.2.13487, or 2026.3 before 2026.3.15863). (source: https://advisories.octopus.com/post/2026/sa2026-20/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-93487 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-93487 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-20
- https://advisories.octopus.com/post/2026/sa2026-20/
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.

Entry: https://cve.now/CVE-2026-93487
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-93487.

Timeline

Nov 11, 2026, 7:21 AM UTCCVE published
Nov 11, 2026, 7:28 AM UTCFirst seen by cve.now

Affected versions

Octopus Deploy Octopus Server
From 2019.11.0 · fixed in 2026.2.13487; From 2026.3.0 · fixed in 2026.3.15863

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Link
advisories.octopus.com · post/2026/sa2026-20

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-93487
Record
NVD · CVE-2026-93487

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-93487

Is CVE-2026-93487 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?

Octopus Server does not correctly validate the permissions assigned to a user. As a result, a user can run runbooks or create deployments they are not authorised to perform.Source: advisories.octopus.com

Which versions are affected by CVE-2026-93487?

Octopus Server: from 2019.11.0 before 2026.2.13487; from 2026.3.0 before 2026.3.15863.Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are 2019.x from 2019.11 onward, 2020.x through 2025.x, 2026.x before 2026.2.13487, and 2026.3 before 2026.3.15863. The version shown in the Octopus Server web portal can be compared against these ranges.Source: advisories.octopus.com

How do I fix CVE-2026-93487?

Upgrade to 2026.2.13487 or later if on the 2026.2 line, or to 2026.3.15863 or later if on the 2026.3 line. Older releases in the affected ranges have no listed fix and need an upgrade to a fixed build.Source: advisories.octopus.com

In affected versions of Octopus Server, incorrect validation of the permissions assigned to a user that would allow them to create project…