Octopus Server: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
CVE-2026-96414 is a high-severity reliance on obfuscation or encryption of security-relevant inputs without integrity checking vulnerability in Octopus Server from Octopus Deploy, with a CVSS 4.0 base score of 8.7 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 2026.2.13487, 2026.3.15875 as the first without the flaw, so updating Octopus Server to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Octopus Server to 2026.2.13487 or 2026.3.15875, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Octopus Deploy | Octopus Server | 2022.1.3143 up to, but not including, 2026.2.13487; 2026.3.0 up to, but not including, 2026.3.15875 | 2026.2.13487, 2026.3.15875 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- NoneNo loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (octopus.com).
Official description
In affected versions of Octopus Server, insufficient integrity protection of authentication cookies, combined with incorrect validation of permissions assigned to a user that allowed them to view users or audit events, could result in the user escalating their privileges to those of an Administrator.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.
How developers prevent this class of flaw
- Protect important client controllable tokens/parameters for integrity using PKI methods (i.e. digital signatures) or other means, and checks for integrity on the server side.
- Repeated requests from a particular user that include invalid values of tokens/parameters (those that should not be changed manually by users) should result in the user account lockout.
- Client side tokens/parameters should not be such that it would be easy/predictable to guess another valid state.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Octopus Server
- 8.7 High severity
- 8.7 High severity
- 8.7 High severity
- 7.1 High severity
- 7.7 High severity
- 7.7 High severity
Recent Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking vulnerabilities
- 8.2 High severity
- 7.7 High severity
- 8.8 High severity
Spotted an error? Tell us.