Account reactivation via empty refresh-token check
Published Aug 13, 2026 · Updated Aug 13, 2026
Incorrect authorization in Gitea 1.26.4 and earlier allows remote authenticated users to reactivate deactivated accounts through OAuth2. The handleOAuth2SignIn gate treats an empty stored refresh token as proof that auto-sync disabled the user, then writes IsActive=true. A deactivated user with a linked GitHub or no-refresh-token OAuth2 account can regain the account's prior access; Prohibit Login remains enforced.
Summary
What happened
Incorrect authorization in Gitea 1.26.4 and earlier allows remote authenticated users to reactivate deactivated accounts through OAuth2. The handleOAuth2SignIn gate treats an empty stored refresh token as proof that auto-sync disabled the user, then writes IsActive=true. A deactivated user with a linked GitHub or no-refresh-token OAuth2 account can regain the account's prior access; Prohibit Login remains enforced.
The record
- CVE
- CVE-2026-55987
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.26.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA-vrhc-jjfc-m3m3 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo