CVE
Octopus Server authorization bypass in LDAP identity validation
Only affects Octopus Server instances with LDAP authentication enabled and LDAP groups mapped to Octopus teams. Fixed in 2026.3.15926.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.13526, 2026.3.15926
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. LDAP authentication is enabled on the Octopus Server instance LDAP groups are mapped to Octopus teams
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 22nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Octopus Server is affected by a flaw in how it checks the external identity linked to a newly registered user, so an attacker with low-privilege access over the network can get the LDAP-mapped team memberships and permissions of another user. The issue only affects instances that have LDAP authentication enabled and LDAP groups mapped to Octopus teams.
Read the original 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.
Who should check
Teams running Octopus Server with LDAP authentication enabled and LDAP groups mapped to Octopus teams.
Read the source excerpt
“This issue only affects instances with LDAP authentication enabled and LDAP groups mapped to Octopus teams.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
LDAP authentication is enabled on the Octopus Server instance LDAP groups are mapped to Octopus teamsUpgrade to a fixed version: 2026.2.13526, 2026.3.15926.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124627 (In affected versions of Octopus Server, incorrect validation of the external identity linked to a newly registered user could result in…), 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-124627 (entry last updated 2026-11-12):
Affected:
- Octopus Deploy Octopus Server: from 3.0.0, fixed in 2026.2.13526; from 2026.3.0, fixed in 2026.3.15926
Fixed versions: 2026.2.13526, 2026.3.15926.
Conditions (all must be true for the bug to be hit):
- LDAP authentication is enabled on the Octopus Server instance (source: https://advisories.octopus.com/post/2026/sa2026-23/)
- LDAP groups are mapped to Octopus teams (source: https://advisories.octopus.com/post/2026/sa2026-23/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-124627 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124627 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-23
- https://advisories.octopus.com/post/2026/sa2026-23/
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-124627
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-124627"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Octopus Deploy Octopus Server
From 3.0.0 · fixed in 2026.2.13526; From 2026.3.0 · fixed in 2026.3.15926
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124627
Is CVE-2026-124627 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: cve.now feed data
What does this mean?
A newly registered user could receive the LDAP-mapped team memberships and permissions of another user, because the external identity linked to the new account was not validated correctly.Source: advisories.octopus.com
Which versions are affected by CVE-2026-124627?
Octopus Server: from 3.0.0 before 2026.2.13526; from 2026.3.0 before 2026.3.15926.Source: cve.now feed data
Am I affected, and how do I check?
The product ranges cover Octopus Server from 3.0.0 up to but not including 2026.2.13526, and from 2026.3.0 up to but not including 2026.3.15926. The issue only applies when LDAP authentication is enabled and LDAP groups are mapped to Octopus teams, so check the Octopus Server version and those two settings on the instance.Source: advisories.octopus.com
How do I fix CVE-2026-124627?
Upgrade Octopus Server to 2026.3.15926 or higher, which the advisory says is not affected.Source: advisories.octopus.com