Casdoor doesn't verify that a JWT used for token exchange is still active (CVE-2026-9097)
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.
AI Analysis
Technical Summary
Casdoor before version 2.362.0 contains a critical vulnerability (CVE-2026-9097) where the GetTokenExchangeToken() function fails to verify if a JWT used for token exchange has been revoked or invalidated. While the JWT signature and claims are validated, the absence of a revocation check against the Token table means that compromised or revoked tokens remain accepted by the system. This undermines session termination and token revocation mechanisms, potentially allowing unauthorized access to protected resources.
Potential Impact
Because the system does not check token revocation status, attackers or unauthorized users may continue to use tokens that should have been invalidated. This can lead to unauthorized access, data compromise, and persistence of active sessions that administrators cannot terminate. The vulnerability affects confidentiality, integrity, and availability of the system, as indicated by the CVSS vector (C:H/I:H/A:H).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should be aware that token revocation is ineffective in affected versions. Monitoring for updates from the Casdoor project is recommended to apply any forthcoming patches promptly.
Casdoor doesn't verify that a JWT used for token exchange is still active (CVE-2026-9097)
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.
CVSS v3.1
Score 9.8critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Casdoor before version 2.362.0 contains a critical vulnerability (CVE-2026-9097) where the GetTokenExchangeToken() function fails to verify if a JWT used for token exchange has been revoked or invalidated. While the JWT signature and claims are validated, the absence of a revocation check against the Token table means that compromised or revoked tokens remain accepted by the system. This undermines session termination and token revocation mechanisms, potentially allowing unauthorized access to protected resources.
Potential Impact
Because the system does not check token revocation status, attackers or unauthorized users may continue to use tokens that should have been invalidated. This can lead to unauthorized access, data compromise, and persistence of active sessions that administrators cannot terminate. The vulnerability affects confidentiality, integrity, and availability of the system, as indicated by the CVSS vector (C:H/I:H/A:H).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should be aware that token revocation is ineffective in affected versions. Monitoring for updates from the Casdoor project is recommended to apply any forthcoming patches promptly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-339w-3hqm-9pjc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-9097"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a46ecbe27e9c7971943d0ba
Added to database: 07/02/2026, 22:57:02 UTC
Last enriched: 07/02/2026, 23:15:40 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.