WSO2 API Control Plane OAuth2 Token Introspection improper authorization

Summaryinfo

A vulnerability, which was classified as problematic, was found in WSO2 API Control Plane, API Manager, Identity Server, Open Banking AM, Open Banking IAM, Traffic Manager and Universal Gateway. The affected element is an unknown function of the component OAuth2 Token Introspection. Such manipulation leads to improper authorization. This vulnerability is uniquely identified as CVE-2026-3583. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in WSO2 API Control Plane, API Manager, Identity Server, Open Banking AM, Open Banking IAM, Traffic Manager and Universal Gateway. It has been rated as problematic. Affected by this issue is some unknown functionality of the component OAuth2 Token Introspection. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is availability. CVE summarizes:

When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately before a revocation request may be returned again to the client after revocation, until the relevant cache entry is cleared. The security consequence is that a revoked access token may be re-issued to the client during the cache lifetime. While the re-issued token is not treated as valid for API authorization, affected users may be unable to obtain a new valid access token until the cache is cleared, which can disrupt authentication flows.

The advisory is shared for download at security.docs.wso2.com. This vulnerability is handled as CVE-2026-3583 since 03/05/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/28/2026). The MITRE ATT&CK project declares the attack technique as T1548.002.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Banking Software

Vendor

• WSO2

Name

• API Control Plane
• API Manager
• Identity Server
• Open Banking AM
• Open Banking IAM
• Traffic Manager
• Universal Gateway

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion