CVE-2026-3236: Octopus Server · Incorrect Authorization
Affects Octopus ServerSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 2025.4.10409 or 2025.3.14761 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.4.10409, 2025.3.14761
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Octopus Server to 2025.4.10409 or 2025.3.14761.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Octopus DeployOctopus Server | Affected
| Fixed in
|
| Octopus DeployOctopus Server | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-3236, organizations should: 1) Restrict the issuance and distribution of access tokens and API keys to the minimum necessary scope and lifetime. 2) Regularly audit API keys and access tokens for unusual creation patterns or extended lifetimes. 3) Implement strict role-based access controls (RBAC) to limit which users or services can create API keys. 4) Monitor Octopus Server logs for anomalous API key creation activities. 7) Educate administrators and developers about the risks of token misuse and enforce secure credential management practices. 8) Employ network segmentation and firewall rules to limit access to Octopus Server APIs from untrusted networks.
Description
In affected versions of Octopus Server it was possible to create a new API key from an existing access token resulting in the new API key having a lifetime exceeding the original API key used to mint the access token.