Improper Token Revocation via OAuth2 Scope Enforcement in Multiple WSO2 Products [Disrupted Authentication Flows]
CVSS score
3.1
EPSS probability
—
Risk score
0.3
Published
2 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
DayBreach AI Explanation
Verified against sourcesSources read
1
Source agreement
Tam uyum
Evidence confidence
%53
Short explanation
In multiple WSO2 products, 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, which can disrupt authentication flows.
The potential re-issuance of a revoked access token to the client during its cache lifetime prevents affected users from obtaining a new valid access token until the cache is cleared, disrupting authentication flows.
What should be done?
- Follow the vendor advisory.
- Review the corresponding WSO2 security advisory document.
- Monitor cache expiration handling.
The sources give limited detail on some technical conditions. Review the chain of evidence below before deciding how to act.
Chain of evidence and sources
allowed_scopes yapılandırması etkin olduğunda, OAuth2 jeton iç gözlem mekanizması iptal isteği sonrasında önbellekteki bir jetonu hemen geçersiz kılmamaktadır.
İptal edilen bir erişim jetonu, ilgili önbellek girdisi temizlenene kadar istemciye tekrar döndürülebilmektedir.
Bu güvenlik sorunu etkilenen kullanıcıların yeni geçerli bir erişim jetonu almasını engelleyerek kimlik doğrulama akışlarını aksatabilmektedir.
Show the technical text from the sources
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.
CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
CWE: CWE-613
This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-3583 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | wso2 | WSO2 API Manager | View |
| 2 | wso2 | WSO2 Traffic Manager | View |
| 3 | wso2 | WSO2 Universal Gateway | View |
| 4 | wso2 | WSO2 API Control Plane | View |
| 5 | wso2 | WSO2 Identity Server | View |
| 6 | wso2 | WSO2 Open Banking IAM | View |
| 7 | wso2 | WSO2 Identity Server as Key Manager | View |
| 8 | wso2 | WSO2 Open Banking AM | View |
| 9 | wso2 | WSO2 Carbon OAuth | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| 3.1 | CVSS V3_1 | LOW | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | CVE CNA |
| 3.1 | CVSS V31 | LOW | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L | NVD |
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-3583 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-3583 weaknesses.
Attack Vector and Accessibility
Official Sources and Advisories
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-3583"