CVE-2026-3583: When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediat
CVE-2026-3583 is a low-severity flaw (CVSS 3.1) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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-i
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 3.1 (Low) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | n/a |
| CISA exploited list | No |
| Weakness | CWE-613 |
| Published | 2026-10-28 |
| Last modified | 2026-10-28 |
Last updated 2026-10-28 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-3583?
No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.
Is CVE-2026-3583 being exploited?
CVE-2026-3583 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-3583 affect?
CVE-2026-3583 affects affected software. Severity is low (CVSS 3.1). 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 introspe
How urgent is CVE-2026-3583?
Priority 11/100. No elevated risk signals yet.