Quick answers
- Is CVE-2026-124627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124627 being exploited in the wild.
- How severe is CVE-2026-124627?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- Octopus Deploy Octopus Server All 3.x, 4.x, 2018.x–2026.1.x, 2026.2.x before 2026.2.13526, 2026.3.x before 2026.3.15926.
- Is there a fix for CVE-2026-124627?
- Yes: fixed in Octopus Server 2026.2.13526, 2026.3.15926 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124627 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-124627?
- 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.15926 or later
Technical details
An LDAP identity injection flaw in Octopus Server fails to properly validate the external identity associated with newly registered users, allowing an attacker to spoof LDAP group membership during account creation. The vulnerability requires LDAP authentication to be enabled and LDAP groups to be mapped to Octopus teams; exploitation grants the attacker arbitrary team memberships and associated permissions without authentication bypass. Fixes are available in versions 2026.2.13526, 2026.3.15926, and later.
Affected products
- Octopus Deploy Octopus Server All 3.x, 4.x, 2018.x–2026.1.x, 2026.2.x before 2026.2.13526, 2026.3.x before 2026.3.15926
Timeline
- 2026-08-28: disclosed: Discovery date
- 2026-10-12: patched: Patch release date
- 2026-11-12: advisory: Advisory release date