In affected versions of Octopus Server, insufficient integrity protection of authentication cookies, combined with incorrect validation of…
Octopus Server 2022.x after 2022.1.3143, all 2023.x to 2025.x, 2026.x before 2026.2.13487, and 2026.3 before 2026.3.15875 are affected. Fixed in 2026.2.13487 and 2026.3.15875.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.13487, 2026.3.15875
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Octopus Server versions 2022.x after 2022.1.3143, all 2023.x, 2024.x and 2025.x, 2026.x before 2026.2.13487, and 2026.3 before 2026.3.15875 are affected. Where guest access is enabled, the attack can be run as the guest user, which raises severity to Critical.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Octopus Server from Octopus Deploy is affected by a flaw in which weak integrity protection of authentication cookies, combined with incorrect permission checks, lets a low-privileged logged-in user, reachable over the network, escalate their privileges to Administrator. The attacker must already have a valid login, and no user interaction is needed.
Read the original 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.
Who should check
Teams running Octopus Server 2022.x (after 2022.1.3143), 2023.x, 2024.x, 2025.x, or 2026.x before the patched builds, on Linux or Windows.
Read the source excerpt
“Customers who have downloaded and installed any of the Octopus Server versions listed below ("Details") are affected.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Octopus Server versions 2022.x after 2022.1.3143, all 2023.x, 2024.x and 2025.x, 2026.x before 2026.2.13487, and 2026.3 before 2026.3.15875 are affected. Where guest access is enabled, the attack can be run as the guest user, which raises severity to Critical.Upgrade to a fixed version: 2026.2.13487, 2026.3.15875.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-96414 (In affected versions of Octopus Server, insufficient integrity protection of authentication cookies, combined with incorrect validation of…), 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-96414 (entry last updated 2026-11-11): Affected: - Octopus Deploy Octopus Server: from 2022.1.3143, fixed in 2026.2.13487; from 2026.3.0, fixed in 2026.3.15875 Fixed versions: 2026.2.13487, 2026.3.15875. Conditions (all must be true for the bug to be hit): - Octopus Server versions 2022.x after 2022.1.3143, all 2023.x, 2024.x and 2025.x, 2026.x before 2026.2.13487, and 2026.3 before 2026.3.15875 are affected. (source: https://advisories.octopus.com/post/2026/sa2026-19/) - Where guest access is enabled, the attack can be run as the guest user, which raises severity to Critical. (source: https://advisories.octopus.com/post/2026/sa2026-19/) 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-96414 is not listed as of cve.now's last read. This KEV status is for CVE-2026-96414 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-19 - https://advisories.octopus.com/post/2026/sa2026-19/ 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-96414 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-96414.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- Octopus Deploy Octopus Server
From 2022.1.3143 · fixed in 2026.2.13487; From 2026.3.0 · fixed in 2026.3.15875
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-96414
Is CVE-2026-96414 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: cve.now feed data
What does this mean?
Authentication cookies are not protected well enough against tampering, and incorrect validation lets a forged cookie be accepted. A user who can view users or audit events can use this to escalate their privileges to Administrator.Source: advisories.octopus.com
Which versions are affected by CVE-2026-96414?
Octopus Server: from 2022.1.3143 before 2026.2.13487; from 2026.3.0 before 2026.3.15875.Source: cve.now feed data
Am I affected, and how do I check?
Octopus Server 2022.x after 2022.1.3143, all 2023.x, 2024.x and 2025.x, 2026.x before 2026.2.13487, and 2026.3 before 2026.3.15875 are affected. Where guest access is enabled, the attack can run as the guest user, which the advisory says raises severity to Critical; check the version under the server's About or Configuration page and whether guest access is enabled in the settings.Source: advisories.octopus.com
How do I fix CVE-2026-96414?
Upgrade Octopus Server to 2026.2.13487 or later on the 2026.2 line, or to 2026.3.15875 or later on the 2026.3 line. Versions 2022.x, 2023.x, 2024.x and 2025.x are affected and no fixed release is listed for them in the checked facts.Source: advisories.octopus.com