Incomplete OAuth Token Revocation via Case Mismatch in WSO2 Identity Server Allows Continued Access After Lifecycle Events
Impact
WSO2 Identity Server versions 7.2.0 to 7.2.0.20 and WSO2 Carbon OAuth versions 7.0.385 to 7.0.385.16 are affected by a vulnerability where OAuth token revocation fails due to case mismatches in usernames, allowing continued access after lifecycle events. A malicious actor with a valid access or refresh token can exploit this. The vulnerability occurs in deployments with case-insensitive user stores and case-sensitive databases.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.What to do
Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5387/#solution
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
WSO2 · WSO2
WSO2 Identity Server
1 range
WSO2 · WSO2
WSO2 Identity Server
Compare with this publisher’s ranges. This does not inspect your installation.
affected
7.2.0 → before 7.2.0.21
custom versions
Other versions: unaffected
WSO2 · WSO2
WSO2 Carbon OAuth
2 ranges
WSO2 · WSO2
WSO2 Carbon OAuth
Compare with this publisher’s ranges. This does not inspect your installation.
affected
7.0.385 → before 7.0.385.17
custom versions
unaffected
7.5.23 → through *
custom versions
Other versions: unknown
Original source description
In deployments of WSO2 Identity Server configured with a case-insensitive user store and a case-sensitive database for identity data, mismatches in username case handling can occur. This inconsistency results in OAuth token revocation operations failing to correctly identify usernames containing mixed-case characters during certain lifecycle events, preventing tokens from being invalidated.
A malicious actor can exploit this vulnerability by possessing a valid access or refresh token associated with a mixed-case username. In affected configurations, these tokens may not be revoked when expected. The actor can then leverage these unrevoked tokens, before their expiry, to continue performing actions that should have been restricted, effectively bypassing intended access controls.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-6647View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
WSO2 · platform conditions
Any condition may hold
Any condition may hold
Vulnerable product
cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*From (inclusive): 7.2.0
Before: 7.2.0.21
Any condition may hold
Vulnerable product
cpe:2.3:a:wso2:wso2_carbon_oauth:*:*:*:*:*:*:*:*From (inclusive): 7.0.385
Before: 7.0.385.17
Required environment
cpe:2.3:a:wso2:wso2_carbon_oauth:*:*:*:*:*:*:*:*From (inclusive): 7.5.23
Through (inclusive): *
Original applicability statements
[
{
"operator": "OR",
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:wso2:wso2_identity_server:*:*:*:*:*:*:*:*",
"versionStartIncluding": "7.2.0",
"versionEndExcluding": "7.2.0.21"
}
]
},
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:wso2:wso2_carbon_oauth:*:*:*:*:*:*:*:*",
"versionStartIncluding": "7.0.385",
"versionEndExcluding": "7.0.385.17"
},
{
"vulnerable": false,
"criteria": "cpe:2.3:a:wso2:wso2_carbon_oauth:*:*:*:*:*:*:*:*",
"versionStartIncluding": "7.5.23",
"versionEndIncluding": "*"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.