Quick answers
- Is CVE-2026-78210 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78210 being exploited in the wild.
- How severe is CVE-2026-78210?
- Informational severity, published 1 October 2026.
- Which products and versions are affected?
- Octopus Deploy Octopus Server 2019.x after 2019.5.9; all 2020.x, 2021.x, 2022.x, 2023.x, 2024.x, 2025.x; 2026.1.x before 2026.1.11739; 2026.2.x before 2026.2.13364; 2026.3.x before 2026.3.13951.
- Is there a fix for CVE-2026-78210?
- Yes: fixed in 2026.1.11739, 2026.2.13364, 2026.3.13951. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78210 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-78210?
- 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: 2026.1.11739, 2026.2.13364, 2026.3.13951
Technical details
An authorization bypass vulnerability in Octopus Server permits users with certain scoped permission sets to execute arbitrary scripts in environments without the required authorization level. This is an access control flaw affecting deployment and script execution workflows. A fix is available in 2026.1.11739, 2026.2.13364, 2026.3.13951, and later versions.
Affected products
- Octopus Deploy Octopus Server 2019.x after 2019.5.9; all 2020.x, 2021.x, 2022.x, 2023.x, 2024.x, 2025.x; 2026.1.x before 2026.1.11739; 2026.2.x before 2026.2.13364; 2026.3.x before 2026.3.13951
Timeline
- 2026-08-17: disclosed: Discovery date (internal testing)
- 2026-08-24: patched: Patch release date
- 2026-09-30: advisory: Advisory release date