CVE-20XX-?

CVE-2026-3583

3.1 LOW 0.3% exploit odds No fix listed Other Web app

What it is

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.

At a glance

Exploitability
Can be exploited over the network with a low-privilege account. Limited direct impact.
Exploit odds
0.3% chance of exploitation in the next 30 days (EPSS).
Fix
No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Details

Published
Last modified
Exploit probability
0.3% · EPSS, next 30 days
Weakness
CWE-613
Record status
Awaiting Analysis

Attack profile CVSS 3.1 · 3.1

Attack vector
Network
Complexity
High
Privileges needed
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
Raw vector

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

Meme: I wake up, CVE-2026-3583
Download Square Reddit

References

NVD record · CVE.org record