CVE-2026-9094
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCasdoor 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe GetTokenExchangeToken function in Casdoor's object/token_oauth.go validates JWT signatures but fails to verify that the token's user belongs to the same organization as the target application, allowing authenticated users to exchange tokens across organizational boundaries and achieve privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Casdoor is installedCheck for the casdoor binary in common locations (/usr/bin/casdoor, /usr/local/bin/casdoor) or look for a running process named 'casdoor' using commands like 'ps aux | grep casdoor' or 'docker ps' if running in a containerAffected if Casdoor is not present on the system
-
Identify the installed Casdoor versionRun 'casdoor --version' or 'casdoor -v' if the binary supports it, or check the version from the binary metadata: 'casdoor -version' or inspect the Docker image tag if running in a containerAffected if The version is 2.362.0 or earlier, or the version cannot be determined but is known to be old
-
Verify token exchange feature is enabledExamine the Casdoor configuration file (typically conf/app.conf or similar) for OAuth-related settings, specifically look for 'enableOAuth' or 'tokenExchange' configuration sections, or check if there are any OAuth applications configured in the Casdoor web interface under the Applications sectionAffected if OAuth and token exchange features are enabled and configured with applications in multiple organizations
-
Check for multi-organization OAuth applicationsReview the Casdoor web interface or database to list existing OAuth applications and their organization affiliations. Look for applications belonging to different organizations that could be targets for cross-organization token exchangeAffected if Multiple OAuth applications exist across different organizations with token exchange capability enabled
A user is affected if they are running Casdoor version 2.362.0 or earlier with OAuth/token exchange enabled and have applications in multiple organizations, allowing an authenticated user from one organization to potentially exchange tokens to access applications in another organization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Casdoor to a version newer than 2.362.0 that includes proper organization membership verification in the token exchange flow, or add organization ownership validation to the GetTokenExchangeToken function before issuing tokens.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data