The system fails to invalidate existing access tokens associated with sub-organization users during sensitive account management operations such as password reset, role change, or sub-organization disablement
Source GCVE Database
Not known to be exploited · CVSS 7.4 High : upgrade to 7.0.0.85 soon.
Data as of 30 Oct 2026, 20:25 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.4 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.0.0.85, 7.0.26.51
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade WSO2 Identity Server to 7.0.0.85; WSO2 Carbon OAuth to 7.0.26.51; org.wso2.identity.server/wso2-identity-server to 7.0.26.51 or 7.0.0.85.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WSO2WSO2 Identity Server | Affected
| Fixed in
|
| WSO2 Carbon OAuthorg.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth | Affected
| Fixed in
|
Mavenorg.wso2.identity.server/wso2-identity-serverpkg:maven/org.wso2.identity.server/wso2-identity-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The system fails to invalidate existing access tokens associated with sub-organization users during sensitive account management operations such as password reset, role change, or sub-organization disablement. This oversight allows previously issued tokens to remain active even after the user's access context has been modified or revoked through administrative actions. The identified issue could lead to unauthorized access by a malicious actor, but only when all of the following conditions are met: previously issued access tokens remain active, and these tokens have been exposed to malicious actors.