cve.bz

CVE-2026-6647 wso2: Insufficient Session Expiration

7.4 highEPSS 0.2%Fix available

High (7.4) in wso2. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • WSO2 WSO2 Carbon OAuth: fixed in 7.5.23

Ask an AI about this CVE

Show the promptExplain CVE-2026-6647 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6647?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6647?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6647 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • wso2:wso2 carbon oauth
  • wso2:wso2 identity server

Versions

From the CNA's record in the CVE List.

ProductAffected
WSO2 Identity Serverfrom 7.2.0 before 7.2.0.21
WSO2 Carbon OAuthfrom 7.0.385 before 7.0.385.17

Fixed in

ProductFixed in
WSO2 Carbon OAuth7.5.23

References

Check your stackJSON