Inconsistent OIDC Token Issuer Validation Allows Unauthorized Token Acceptance
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Octopus Deploy | Octopus Server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Octopus | Octopus Server |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.226% probability within 30 days)
| Link | Providers |
|---|---|
| https://advisories.octopus.com/post/2026/sa2026-15 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Octopus
Octopus octopus Server |
|
| Vendors & Products |
Octopus
Octopus octopus Server |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Inconsistent OIDC Token Issuer Validation Allows Unauthorized Token Acceptance |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Weaknesses | CWE-1289 | |
| References |
| |
| Metrics |
cvssV4_0
|