CVE-2026-128359

Gitea OAuth2 provider tokens issued to disabled users

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.

Analysis

AI-generated

Technical impact

The vulnerability occurs because Gitea's OAuth2 and OpenID Connect provider token endpoint does not verify whether the user account is enabled or disabled. When an administrator deactivates an account, the existing refresh tokens and unused authorization codes for that account can still be exchanged for new tokens, allowing applications that rely on Gitea for authentication to keep the user signed in. This flaw enables unauthorized continued access or session hijacking for users who should no longer be able to authenticate.

Affected Systems

The affected product is Gitea, a single product named Gitea. Versions affected are all releases prior to the 28.4.0 patch that introduced the check for user state in the token endpoint. The release notes and blog post for version 28.4.0 confirm the fix, so users running an earlier release are likely vulnerable.

Risk and Exploitability

Risk is elevated because attackers who possess a refresh token or authorization code for a disabled account can repeatedly request new tokens. The EPSS score is not available and the vulnerability is not currently listed in the CISA KEV catalog, but the lack of user state validation still represents a significant authentication bypass. The attack vector is through the standard OAuth2 token endpoint which is commonly exposed by applications, making exploitation straightforward once a token is in an attacker's possession.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.4.0 or later to apply the official fix that checks user state during token issuance.
  • After upgrading, audit your OAuth2 user base to identify any disabled accounts that might still possess active refresh tokens or authorization codes and revoke those tokens.
  • Implement regular token revocation or rotation policies to reduce the window of opportunity for tokens issued before the patch to remain valid.

Generated by OpenCVE AI on November 15, 2026 at 22:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.
Title Gitea OAuth2 provider tokens issued to disabled users
Weaknesses CWE-613
References
Weaknesses
  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:14 PM
Reserved
Nov 15, 2026, 8:31 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM