CVE
Octopus Server authorization bypass in LDAP identity editing
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.13526, 2026.3.15936
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Octopus Server versions in the affected ranges (2018.3.x through 2026.1.x, 2026.2.x before 2026.2.13526, 2026.3.x before 2026.3.15936). Requires that an Administrator has disabled self-service identity editing for LDAP identities.
- 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.21% · 10th 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
In Octopus Server by Octopus Deploy, incorrect validation of changes to a user's own LDAP identity lets a logged-in user edit that identity even when an administrator has disabled self-service editing. A remote attacker with a low-privilege account can use this to join teams mapped to LDAP groups they do not belong to, which could escalate to full administrative access if any of those teams are privileged.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In affected versions of Octopus Server, incorrect validation of changes a user made to their own LDAP identity allowed them to edit that identity even when an Administrator had disabled self-service identity editing. This could result in the user gaining membership of teams mapped to external LDAP groups they do not belong to, and potentially escalating to full administrative privileges if any of those teams are privileged.
Who should check
Teams running Octopus Server with LDAP authentication where administrators have disabled self-service LDAP identity editing, across all listed 2018.3.x through 2026.3.x versions.
Read the source excerpt
“All 2018.3.x, 2019.x, 2020.x, 2021.x, 2022.x, 2023.x versions”
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.
Octopus Server versions in the affected ranges (2018.3.x through 2026.1.x, 2026.2.x before 2026.2.13526, 2026.3.x before 2026.3.15936). Requires that an Administrator has disabled self-service identity editing for LDAP identities.Upgrade to a fixed version: 2026.2.13526, 2026.3.15936.
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-124628 (In affected versions of Octopus Server, incorrect validation of changes a user made to their own LDAP identity allowed them to edit that…), 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-124628 (entry last updated 2026-11-12):
Affected:
- Octopus Deploy Octopus Server: from 2018.3.0, fixed in 2026.2.13526; from 2026.3.0, fixed in 2026.3.15936
Fixed versions: 2026.2.13526, 2026.3.15936.
Conditions (all must be true for the bug to be hit):
- Octopus Server versions in the affected ranges (2018.3.x through 2026.1.x, 2026.2.x before 2026.2.13526, 2026.3.x before 2026.3.15936). (source: https://advisories.octopus.com/post/2026/sa2026-24/)
- Requires that an Administrator has disabled self-service identity editing for LDAP identities. (source: https://advisories.octopus.com/post/2026/sa2026-24/)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-124628 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124628 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-24
- https://advisories.octopus.com/post/2026/sa2026-24/
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-124628
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-124628"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Octopus Deploy Octopus Server
From 2018.3.0 · fixed in 2026.2.13526; From 2026.3.0 · fixed in 2026.3.15936
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-124628
Is CVE-2026-124628 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?
Octopus Server did not properly check changes a user made to their own LDAP identity. Even when an Administrator had disabled self-service identity editing for LDAP identities, a user could still edit that identity. This could give the user membership of teams mapped to LDAP groups they do not belong to, and potentially full administrative privileges if those teams are privileged.Source: advisories.octopus.com
Which versions are affected by CVE-2026-124628?
Octopus Server: from 2018.3.0 before 2026.2.13526; from 2026.3.0 before 2026.3.15936.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are Octopus Server 2018.3.x through 2026.1.x, 2026.2.x before 2026.2.13526, and 2026.3.x before 2026.3.15936. The setup involves LDAP identities with self-service identity editing disabled by an Administrator. To check a version, look at the Octopus Server version shown in the web portal or the server's version information.Source: advisories.octopus.com
How do I fix CVE-2026-124628?
Upgrade to Octopus Server 2026.2.13526 or 2026.3.15936, depending on the release line in use. These are the fixed versions named by the vendor.Source: advisories.octopus.com