CVE-2026-3237 Vulnerability Analysis & Exploit Intelligence

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.

Published Mar 17, 2026Updated Mar 17, 2026Sources: cvelistV5, Octopus

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

octopus deploy

octopus_server

CVSS base

2.3

LOW

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

octopus deploy

Products (1)

octopus server

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
2.3	CVSS 4.0	LOW	—	—	cvelistV5

Weakness & attack patterns

CWE-285

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
T1083File and Directory Discovery
T1562.003Impair Defenses: Impair Command History Logging

References

1 on the record

advisories.octopus.com/post/2026/sa2026-03
reference

Elsewhere on this site

octopus deployevery CVE for this vendor
CWE-285other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.