Quick answers
- Is CVE-2026-96414 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96414 being exploited in the wild.
- How severe is CVE-2026-96414?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Octopus Deploy Octopus Server 2022.1.3143+, all 2023.x, 2024.x, 2025.x; 2026.x before 2026.2.13487; 2026.3.x before 2026.3.15875.
- Is there a fix for CVE-2026-96414?
- Yes: fixed in 2026.2.13487, 2026.3.15875. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96414 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-96414?
- 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.2.13487, 2026.3.15875
Technical details
The vulnerability is a combination of insufficient integrity protection on authentication cookies and incorrect permission validation that allows users to access restricted endpoints (user viewing, audit events). An attacker with low privileges can forge authentication cookies and escalate privileges to Administrator. No authentication or user interaction is required beyond network access; if guest access is enabled, exploitation is possible with no credentials.
Affected products
- Octopus Deploy Octopus Server 2022.1.3143+, all 2023.x, 2024.x, 2025.x; 2026.x before 2026.2.13487; 2026.3.x before 2026.3.15875
Timeline
- 2026-09-04: disclosed: Discovery date
- 2026-09-29: patched: Patch release date
- 2026-11-09: advisory: Advisory release date