CVE-2026-9097 affects Casdoor 2.362.0 and earlier. In the token exchange flow, the GetTokenExchangeToken() function in object/token_oauth.go validates the JWT signature and parses claims from the presented subject token, but does not verify against the Token table whether that JWT is still active, revoked, or otherwise invalidated. As a result, token exchange relies on cryptographic validity and claim parsing alone, without enforcing token revocation state. This creates a logic flaw in session and token lifecycle enforcement that allows previously revoked or invalidated JWTs to continue being accepted during token exchange.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.