In affected versions of Octopus Server, incorrect validation of permissions assigned to a user that would allow them to edit their own…

Check whether my systems are affected by CVE-2026-105948 (In affected versions of Octopus Server, incorrect validation of permissions assigned to a user that would allow them to edit their own…), 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-105948 (entry last updated 2026-11-11):
Affected:
- Octopus Deploy Octopus Server: from 2024.2.5035, fixed in 2026.2.13487; from 2026.3.0, fixed in 2026.3.15909
Fixed versions: 2026.2.13487, 2026.3.15909.
Conditions (all must be true for the bug to be hit):
- Instances using LDAP authentication with self-service login editing enabled (source: https://advisories.octopus.com/post/2026/sa2026-21/)
- Affected Octopus Server versions: 2024.2.x after 2024.2.5035, 2024.3.x, 2024.4.x, 2025.x, 2026.1.x, 2026.2.x before 2026.2.13487, and 2026.3.x before 2026.3.15909 (source: https://advisories.octopus.com/post/2026/sa2026-21/)
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.
Workaround: Turn off Allow users to edit their own logins. (source: https://advisories.octopus.com/post/2026/sa2026-21/)
CISA KEV: CVE-2026-105948 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-105948 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-21
- https://advisories.octopus.com/post/2026/sa2026-21/
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-105948
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-105948.