# CVE-2026-116870: In affected versions of Octopus Server, OIDC token issuer validation was performed inconsistently.


- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-j58f-w66m-94wj

## What is CVE-2026-116870?

CVE-2026-116870 is a high-severity vulnerability in Octopus Server, published on 27 Oct 2026. 

### Official 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.

Weakness: CWE-1289 (Improper Validation of Unsafe Equivalence in Input)

## Which versions are affected by CVE-2026-116870?


## How do I fix CVE-2026-116870?

No fix has been published for CVE-2026-116870 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116870 being exploited?

There is no known exploitation of CVE-2026-116870 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116870 and fix it if it is affected.

What it is: CVE-2026-116870 is a high-severity vulnerability in Octopus Server, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116870 in the wild and no public exploit code.

Affected product: Octopus Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116870/ (Markdown: https://insights.sbomify.com/CVE-2026-116870/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116870
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116870
- OSV: https://osv.dev/vulnerability/CVE-2026-116870

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116870/
Summaries are generated and may contain mistakes; the official description above is the record.