Quick answers
- Is CVE-2026-124628 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124628 being exploited in the wild.
- How severe is CVE-2026-124628?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- Octopus Deploy Octopus Server 2018.3.x through 2026.2.13525, 2026.3.x before 2026.3.15936.
- Is there a fix for CVE-2026-124628?
- Yes: fixed in Octopus Server 2026.2.13526, 2026.3.15936. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124628 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-124628?
- Check whether you run Octopus Deploy Octopus Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Octopus Server 2026.2.13526, 2026.3.15936
Technical details
The vulnerability is an incorrect authorization check in LDAP identity modification that allows an authenticated user to edit their own LDAP identity attributes even when the administrator has disabled self-service identity editing. An attacker can exploit this to add themselves to LDAP groups, gaining membership of teams mapped to those groups and potentially assuming administrative roles if any team is privileged. This requires valid user authentication and network access to the Octopus Server instance.
Affected products
- Octopus Deploy Octopus Server 2018.3.x through 2026.2.13525, 2026.3.x before 2026.3.15936
Timeline
- 2026-08-28: disclosed: Discovery date
- 2026-10-13: patched: Patch release date
- 2026-11-12: advisory: Advisory release date