Skip to main content
VulnerabilityPublished

CVE-2026-6647: WSO2 Identity Server · Insufficient Session Expiration

Affects WSO2 Identity ServerSource CVE Database V5

0

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

Data as of 28 Oct 2026, 20:41 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

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

Affected software

ProductAffectedFixed in
WSO2WSO2 Identity ServerAffected
  • >=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.oauthAffected
  • >=7.0.385 <7.0.385.17
Fixed in
  • 7.0.385.17

AI-suggested

Upgrade WSO2 Identity Server to version 7.2.0.21 or later, or 7.0.385.17 or later, where this issue is fixed. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-6647 is a vulnerability in WSO2 Identity Server where inconsistent case handling between a case-insensitive user store and a case-sensitive identity database causes OAuth token revocation failures. Tokens associated with mixed-case usernames may not be properly revoked, allowing continued unauthorized use until token expiry. This affects versions >=7.2.0 <7.2.0.21 and >=7.0.385 <7.0.385.17. A fix is available in versions 7.2.0.21 and 7.0.385.17.

References

Community reviews

Loading reviews…