CVE-2026-101271
Received Received - Intake

OAuth Access Token Persistence After Client Disabling

Publication date: 2026-09-29

Last updated on: 2026-09-29

Assigner: rami.io

Description
OAuth credentials (access tokens) are valid for the entirety of their lifetime, even if the application (OAuth client) they are bound to is manually disabled.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-29
Last Modified
2026-09-29
Generated
2026-09-29
AI Q&A
2026-09-29
EPSS Evaluated
N/A
NVD
CVE-2026-101271
EUVD
EUVD-2026-88754

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves OAuth access tokens remaining valid even after the associated application (OAuth client) is disabled. Normally, disabling an application should revoke access, but these tokens continue to function for their entire lifetime, posing a security risk.

Impact Analysis

If an attacker gains access to a valid token, they could maintain unauthorized access to resources even after the legitimate application is disabled. This could lead to data breaches, unauthorized actions, or prolonged access to sensitive systems.

Compliance Impact

This vulnerability may violate principles of least privilege and access control required by GDPR and HIPAA. It could lead to unauthorized data access, undermining compliance with data protection and security requirements.

Mitigation Strategies

Rotate all OAuth access tokens immediately and revoke any tokens associated with disabled applications. Review token lifetimes and enforce shorter validity periods.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-101271. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart