{"id":"CVE-2026-116870","aliases":[],"title":"In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently.","titleSource":"Octopus","descriptionSource":"Octopus","products":[{"vendor":"Octopus Deploy","name":"Octopus Server","platforms":["Windows","Linux"],"versions":[{"version":"2024.1.0","status":"affected","lessThan":"2026.1.11781","versionType":"custom"},{"version":"2026.2.0","status":"affected","lessThan":"2026.2.13438","versionType":"custom"},{"version":"2026.3.0","status":"affected","lessThan":"2026.3.15816","versionType":"custom"}],"defaultStatus":"unaffected","source":"Octopus","url":"https://www.cve.org/CVERecord?id=CVE-2026-116870"}],"remediation":[],"description":"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.","severity":"high","score":8.7,"published":"2026-10-27T10:28:11.007Z","modified":"2026-10-27T10:28:11.007Z","withdrawn":false,"knownExploited":false,"affected":[],"references":["https://advisories.octopus.com/post/2026/sa2026-15"],"sources":[{"name":"CVE","id":"CVE-2026-116870","modified":"2026-10-27T10:28:11.007Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-116870"}],"assessments":[{"source":"Octopus","vector":"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","score":8.7}],"sourceAffected":[],"kev":{"status":"not-listed","checkedAt":"2026-10-29T06:00:31.558Z"},"coverage":[{"source":"NVD","status":"not-checked"},{"source":"GHSA","status":"not-checked"},{"source":"EUVD","status":"not-checked"},{"source":"EPSS","status":"not-checked"}],"evidence":[]}