In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently. This could result in a token issued from a suitably configured non legitimate issuer being accepted as a token belonging to a service account from a legitimate trusted issuer. Exploitation requires a service account with at least one OIDC identity configured. An attacker would also need to know or guess some details of that identity in order to be in a position to attempt exploitation.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 6
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-27 10:28
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-27 15:08
- StatusReceived → PublishedNVD modified 2026-10-27 10:28
- StatusPublished → ReceivedNVD modified 2026-10-27 11:17
- CVSS8.7 (v4.0, CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) → 8.7 (v4.0, CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X)NVD modified 2026-10-27 11:17
- First seenCVSS 8.7 · octopus deployNVD modified 2026-10-27 10:28
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.