# CVE-2026-9097: CVE-2026-9097

> Attackers can use revoked JWTs for token exchange because Casdoor fails to verify token revocation status, bypassing session termination controls.

- **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-339w-3hqm-9pjc, GO-2026-5892

## What is CVE-2026-9097?

CVE-2026-9097 is a critical 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 do not verify that a JWT used for token exchange is still active. The GetTokenExchangeToken() function in object/token_oauth.go validates the JWT signature and parses its claims, but never queries the Token table to verify whether the subject token has been revoked or invalidated. Because the revocation check is entirely absent, administrators are unable to terminate active sessions or revoke compromised tokens.

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

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 to 1.1000.1-0.20260321120606-239e8bd69487 | None |
| `github.com/casdoor/casdoor` | Go | All versions to 1.1000.1-0.20260321120606-239e8bd69487 | None |

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

Apply the vendor's patch.

## Is CVE-2026-9097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9097 is a critical 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-9097 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 up to 1.1000.1-0.20260321120606-239e8bd69487; no fix listed
- github.com/casdoor/casdoor (Go): affected all versions up to 1.1000.1-0.20260321120606-239e8bd69487; no fix listed

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

## Sources

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

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