# CVE-2026-9094: CVE-2026-9094

> Attackers can exchange tokens across organizations due to missing user validation, leading to privilege escalation in Casdoor identity provider.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-c9w5-qp6m-m395, GO-2026-5953

## What is CVE-2026-9094?

CVE-2026-9094 is a critical authentication bypass vulnerability in Casdoor, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Casdoor versions 2.362.0 and earlier contain a vulnerability enabling cross-organization token exchange. The GetTokenExchangeToken function in object/token_oauth.go validates JWT signatures but does not verify that the token's user belongs to the same organization as the target application. This can result in privilege escalation across organizational boundaries.

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

3 open source packages ship an affected version, including github.com/casdoor/casdoor.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/casdoor/casdoor` | Go | All versions | None |
| `github.com/casdoor/casdoor` | Go | All versions | 2.387.0 |
| `github.com/casdoor/casdoor` | Go | All versions | 2.387.0 |

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

Upgrade github.com/casdoor/casdoor to 2.387.0 or later.

## Is CVE-2026-9094 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9094 is a critical authentication bypass vulnerability in Casdoor, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9094 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/casdoor/casdoor (Go): affected all versions; no fix listed
- github.com/casdoor/casdoor (Go): affected all versions; fixed in 2.387.0
- github.com/casdoor/casdoor (Go): affected all versions; fixed in 2.387.0

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-9094/ (Markdown: https://insights.sbomify.com/CVE-2026-9094/index.md)
```

## Sources

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

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