p PatchFirst

CVE-2026-6647

CVE-2026-6647 · Incomplete OAuth Token Revocation via Case Mismatch in WSO2 Identity Server Allows Continued Access After Lifecycle Events

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 7.4 · High · EPSS 0.2% · Fix available

Published
Updated

Affected products and versions

  • wso2 identity server

    Versions
    • ≥ 7.2.0, < 7.2.0.21: Affected (custom)

    Update to 7.2.0.21

  • wso2 carbon oauth

    Versions
    • ≥ 7.0.385, < 7.0.385.17: Affected (custom)
    • ≥ 7.5.23: Not affected (custom)

    Update to 7.0.385.17

Original sources

Check your server →