WSO2 Identity Server keeps OAuth tokens of mixed-case users valid
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- Low · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-613.
Summary
WSO2 Identity Server from 7.2.0 before 7.2.0.21 and WSO2 Carbon OAuth from 7.0.385 before 7.0.385.17 are affected. With a case-insensitive user store and a case-sensitive database, token revocation misses mixed-case usernames during some lifecycle events, leaving tokens valid (CWE-613). An attacker with low privileges who holds a valid access or refresh token for a mixed-case username can keep using it before expiry to bypass intended access controls.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade WSO2 Identity Server to 7.2.0.21 and WSO2 Carbon OAuth to 7.0.385.17 or 7.5.23.
Written with Claude Haiku 5.5 from the sources below · 2026-11-05
- Fix · CNA WSO2 Identity Server (WSO2) Fixed in 7.2.0.21
- Fix · CNA WSO2 Carbon OAuth (WSO2) Fixed in 7.0.385.17, 7.5.23
Timeline
- 2026-10-28 Threatist record created from CVE-2026-6647
- 2026-10-28 Alias added: GHSA-rxrw-f2xj-7fjx
- 2026-10-29 CISA SSVC decision points changed
- 2026-10-29 Priority changed: MEDIUM → LOW
References
More WSO2 vulnerabilities
- TI-2026-04755 Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account Takeover KEVCVSS 3.1CRITICAL 10.0
- TI-2022-11928 Certain WSO2 products allow unrestricted file upload with resultant remote code execution. KEVCVSS 3.1CRITICAL 9.8
- TI-2022-18808 An issue was discovered in WSO2 Enterprise Integrator 6.4.0. CVSS 3.1MEDIUM 6.1
- TI-2020-15069 The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0… CVSS 3.1CRITICAL 9.1
- TI-2023-15163 A reflected cross-site scripting (XSS) vulnerability in /authenticationendpoint/login.do… CVSS 3.1MEDIUM 6.1
- TI-2022-04130 WSO2 carbon-registry Advanced Search advancedSearchForm-ajaxprocessor.jsp cross site scripting CVSS 3.1MEDIUM 6.1
Sources
- CVE-2026-6647 · CVE Program
- CVE-2026-6647 · NVD
- FIRST EPSS
- GHSA-rxrw-f2xj-7fjx · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences