# CVE-2026-124627: Privilege escalation in Octopus Server

> Octopus Server users with LDAP authentication and LDAP-mapped teams may receive another user's LDAP-mapped team memberships and permissions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-8wrj-pg56-7v73

## What is CVE-2026-124627?

CVE-2026-124627 is a high-severity privilege escalation vulnerability in Octopus Server, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In affected versions of Octopus Server, incorrect validation of the external identity linked to a newly registered user could result in that user receiving the LDAP-mapped team memberships and associated permissions of another user. This issue only affects instances with LDAP authentication enabled and LDAP groups mapped to Octopus teams.

Weakness: CWE-863 (Incorrect Authorization)

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

Only installations with a non-default setting turned on are exposed.


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

No fix has been published for CVE-2026-124627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124627 being exploited?

There is no known exploitation of CVE-2026-124627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124627 and fix it if it is affected.

What it is: CVE-2026-124627 is a high-severity privilege escalation vulnerability in Octopus Server, published on 12 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-124627 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: Octopus Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124627/ (Markdown: https://insights.sbomify.com/CVE-2026-124627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124627
- OSV: https://osv.dev/vulnerability/CVE-2026-124627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124627/
Summaries are generated and may contain mistakes; the official description above is the record.