Quick answers
- Is CVE-2026-93487 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93487 being exploited in the wild.
- How severe is CVE-2026-93487?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Octopus Deploy Octopus Server 2019.11 and later through 2026.2.13486, and 2026.3.x before 2026.3.15863.
- Is there a fix for CVE-2026-93487?
- Yes: fixed in Octopus Server 2026.2.13487, 2026.3.15863. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93487 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-93487?
- Check whether you run Octopus Deploy Octopus Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Octopus Server 2026.2.13487, 2026.3.15863
Technical details
Incorrect validation of permissions for users creating project triggers in Octopus Server allows privilege escalation to perform unauthorized runbook execution and deployment creation. The vulnerability exists in multiple versions from 2019.11 onwards through 2026.2.x and early 2026.3.x builds. An authenticated attacker with project trigger creation permissions can bypass authorization checks via a flawed permission validation mechanism.
Affected products
- Octopus Deploy Octopus Server 2019.11 and later through 2026.2.13486, and 2026.3.x before 2026.3.15863
Timeline
- 2026-11-09: disclosed
- 2026-09-28: patched