Account reactivation via unconditional OAuth callback update
Published Jul 3, 2026 · Updated Jul 3, 2026
Improper authorization in Gitea 1.26.1 and earlier allows remote authenticated users to reactivate disabled accounts through OAuth callbacks. The handleOAuth2SignIn handler treats the local IsActive flag as stale and writes it back as true after a linked identity provider authenticates the user. A linked external identity and an administrator-disabled local account are required; successful exploitation restores a session and the account's repository, organization, and token access.
Summary
What happened
Improper authorization in Gitea 1.26.1 and earlier allows remote authenticated users to reactivate disabled accounts through OAuth callbacks. The handleOAuth2SignIn handler treats the local IsActive flag as stale and writes it back as true after a linked identity provider authenticates the user. A linked external identity and an administrator-disabled local account are required; successful exploitation restores a session and the account's repository, organization, and token access.
The record
- CVE
- CVE-2026-58422
- Published
- Jul 3, 2026
- Updated
- Jul 3, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-284, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2026CVE publishedPublication date reported by the CVE source.
- Jul 3, 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.1
What conditions does exploitation require?
What is affected?
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
- Vendor OAuth callback 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