CVE-2026-6647VulnerabilityPublished 28 Oct 2026

In deployments of WSO2 Identity Server configured with a case-insensitive user store and a case-sensitive database for

Source GCVE Database

Authoritative record:CVE-2026-6647· High 7.4

Not known to be exploited · CVSS 7.4 High : upgrade to 7.2.0.21 soon.

Data as of 28 Oct 2026, 22:13 UTC

CVSS 3.1 base score

7.4High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 7.2.0.21, 7.0.385.17

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-rxrw-f2xj-7fjx

What to do

Upgrade WSO2 to 7.2.0.21 (Identity Server) or 7.0.385.17 (Carbon OAuth).

Affected software

Product	Affected	Fixed in
WSO2WSO2 Identity Server	Affected >=7.2.0 <7.2.0.21	Fixed in 7.2.0.21
WSO2 Carbon OAuthorg.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth	Affected >=7.0.385 <7.0.385.17	Fixed in 7.0.385.17

AI-suggested

If you cannot patch yet, administrators should carefully review their user store and database case sensitivity configurations to avoid mismatches. Monitoring and manual token revocation processes may be necessary to mitigate risk.

Description

WSO2 Identity Server deployments that use a case-insensitive user store alongside a case-sensitive database for identity data may experience failures in OAuth token revocation. This occurs because username case mismatches prevent proper identification of tokens associated with mixed-case usernames, allowing tokens to remain valid beyond intended revocation events. An attacker with a valid token for such a username could exploit this to maintain unauthorized access until token expiry.

Impact

Tokens associated with mixed-case usernames may not be revoked properly, allowing attackers who possess such tokens to maintain unauthorized access until token expiration. This undermines intended access control mechanisms and could lead to continued unauthorized actions within the affected system.

Summary

This vulnerability affects WSO2 Identity Server configurations where the user store is case-insensitive but the underlying database handling identity data is case-sensitive. Due to this inconsistency, OAuth token revocation operations fail to correctly match usernames containing mixed-case characters, resulting in tokens not being revoked as expected during lifecycle events. Consequently, an attacker possessing a valid access or refresh token tied to a mixed-case username can continue to use the token to perform actions that should have been blocked, effectively bypassing access controls. The CVSS 3.1 score is 7.4 (high severity), reflecting network attack vector, low attack complexity, privileges required, no user interaction, scope changed, and partial confidentiality, integrity, and availability impacts.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 22:13 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats