Wso2 Carbon Oauth
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Wso2 Carbon Oauth.
By the Year
In 2026 there have been 2 vulnerabilities in Wso2 Carbon Oauth with an average score of 3.7 out of ten.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 2 | 3.65 |
It may take a day or so for new Wso2 Carbon Oauth vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Wso2 Carbon Oauth Security Vulnerabilities
WSO2 IS Improper Refresh Token Handling in Impersonation Flow
CVE-2025-12627
2.4 - Low
- August 06, 2026
The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their ability to act as the legitimate user. An attacker who gains access to an impersonated user's access token can exploit this weakness to renew their authorization. This results in the continued ability to perform actions on behalf of the actual user, compromising log integrity and traceability by masking the true actor.
Insufficient Session Expiration
Auth Code Leakage in WSO2 Identity Server Allows Token Abuse
CVE-2024-8995
4.9 - Medium
- August 06, 2026
Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and the associated client credentials (client ID and client secret), they can leverage these unused codes to obtain access tokens on behalf of users who have already been deleted. This may lead to unauthorized access to sensitive resources and services, contingent on the scopes originally authorized for the compromised authorization code.
Insufficient Session Expiration
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Wso2 Carbon Oauth or by Wso2? Click the Watch button to subscribe.