CVE-2026-3236
No known exploitation. EPSS puts it in the 17th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- Octopus Deploy Octopus ServerAffected: ≥ 2023.0.0, < 2025.3.14761Upgrade to: 2025.3.14761Affected: ≥ 2025.4.0, < 2025.4.10409Upgrade to: 2025.4.10409Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 17th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 112 days, from the signal feeds we watch.
- OpenVAS check added
- Publishedweakness classified, att&ck mapped, record updated
Affected products
Technical detail
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Octopus Server, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI