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.