Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA WSO2

CVE-2026-3583: Improper Token Revocation via OAuth2 Scope Enforcement in Multiple WSO2 Products [Disrupted Authentication Flows]

Noroxi assessment

Priority: Monitor (action score 12/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

LowCVSS 3.1 · v3.1—No exploit No fix recorded
Published
Oct 28, 2026
Updated
Oct 29, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
12 / 40 · 3.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · WSO2
3.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-3583

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 WSO2 API Control Plane

    • before 4.5.0unknown
    • 4.5.0 and later · before 4.5.0.68affected
    • 4.6.0 and later · before 4.6.0.30affected
    • 4.7.0 and later · before 4.7.0.3affected

  • WSO2 WSO2 API Manager

    • before 3.1.0unknown
    • 3.1.0 and later · before 3.1.0.367affected
    • 3.2.0 and later · before 3.2.0.475affected
    • 3.2.1 and later · before 3.2.1.106affected
    • 4.0.0 and later · before 4.0.0.394affected
    • 4.1.0 and later · before 4.1.0.267affected
    • 4.2.0 and later · before 4.2.0.207affected
    • 4.3.0 and later · before 4.3.0.120affected
    • 4.4.0 and later · before 4.4.0.83affected
    • 4.5.0 and later · before 4.5.0.67affected

  • WSO2 WSO2 Carbon OAuth

    • 6.4.2 and later · before 6.4.2.178affected
    • 6.4.111 and later · before 6.4.111.174affected
    • 6.4.176 and later · before 6.4.176.38affected
    • 6.4.180 and later · before 6.4.180.25affected
    • 6.8.0 and later · before 6.8.0.59affected
    • 6.9.6 and later · before 6.9.6.36affected
    • 6.11.21 and later · before 6.11.21.118affected
    • 6.13.16 and later · before 6.13.16.32affected
    • 6.13.19 and later · before 6.13.19.23affected
    • 6.13.27 and later · before 6.13.27.21affected

  • WSO2 WSO2 Identity Server

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.397affected
    • 5.11.0 and later · before 5.11.0.444affected
    • 6.0.0 and later · before 6.0.0.270affected
    • 6.1.0 and later · before 6.1.0.269affected
    • 7.0.0 and later · before 7.0.0.152affected
    • 7.1.0 and later · before 7.1.0.61affected
    • 7.2.0 and later · before 7.2.0.20affected
    • 7.3.0 and later · before 7.3.0.1affected

  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.387affected

  • WSO2 WSO2 Open Banking AM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.414affected

  • WSO2 WSO2 Open Banking IAM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.434affected

  • WSO2 WSO2 Traffic Manager

    • before 4.5.0unknown
    • 4.5.0 and later · before 4.5.0.65affected
    • 4.6.0 and later · before 4.6.0.29affected
    • 4.7.0 and later · before 4.7.0.3affected

  • WSO2 WSO2 Universal Gateway

    • before 4.5.0unknown
    • 4.5.0 and later · before 4.5.0.67affected
    • 4.6.0 and later · before 4.6.0.29affected
    • 4.7.0 and later · before 4.7.0.3affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-4052Privilege Escalation via Token Endpoint in WSO2 API Manager (APIM 4.x/IS as Resident Key Manager)
    39Monitor
  • CVE-2025-11969Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized Administrative Actions
    37Monitor
  • CVE-2025-14561Access Control Bypass via Publisher REST APIs in Multiple WSO2 Products Allows Cross-Tenant Operations
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-14260Oct 28, 2026 · Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources
    33Monitor
  • ← EarlierCVE-2026-11854Oct 28, 2026 · Cross-Site Scripting via Authentication Endpoint Error Message in Multiple WSO2 Products
    24Monitor
  • Later →CVE-2024-5617Nov 2, 2026 · Account Lock Bypass via User Store Synchronization in Multiple WSO2 Products Allows Brute Force Attacks
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-95175 days apartImproper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts
    19Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

Weakness class (CWE)

CWE-613 · Insufficient Session Expiration

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records