CVE-2026-3583: WSO2 API Manager · Insufficient Session Expiration
Affects WSO2 API ManagerSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low · fixed in 4.7.0.3 : update WSO2 API Manager when convenient.
Data as of 28 Oct 2026, 20:45 UTC
- Patch
- Available – fixed in 4.7.0.3, 4.6.0.29, 4.5.0.67 +38
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
AI-suggested
Fixed versions are available and users should upgrade to one of the following patched releases: 3.2.0.475, 3.2.1.106, 4.0.0.394, 4.1.0.267, 4.2.0.207, 4.3.0.120, 4.4.0.83, 4.5.0.67, 4.6.0.29, or 4.7.0.3. Applying these official fixes will resolve the caching issue and prevent revoked tokens from being re-issued. No additional mitigation is required if these updates are applied.
Description
CVE-2026-3583 is a vulnerability in WSO2 API Manager where the OAuth2 token introspection cache does not immediately invalidate tokens after revocation when the allowed_scopes configuration is enabled. This can cause revoked access tokens to be re-issued to clients during the cache lifetime. Although these re-issued tokens are not valid for API authorization, affected users may face disruptions in obtaining new valid tokens until the cache clears.