How severe is CVE-2026-9097?

CVE-2026-9097 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-9097 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-9097?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-9097 have an EU (EUVD) identifier?

Yes. CVE-2026-9097 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32951.

When was CVE-2026-9097 published?

CVE-2026-9097 was published on 2026-05-28 and last updated on 2026-06-17.

CVE-2026-9097

CVE-2026-9097 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-32951
Published: 2026-05-28
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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.
How severe is CVE-2026-9097?: CVE-2026-9097 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-9097 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-9097?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-9097 have an EU (EUVD) identifier?: Yes. CVE-2026-9097 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-32951.
When was CVE-2026-9097 published?: CVE-2026-9097 was published on 2026-05-28 and last updated on 2026-06-17.

References

https://kb.cert.org/vuls/id/780781