Account takeover via cross-user recovery codes
Published Feb 6, 2026 · Updated Feb 6, 2026
Authentication bypass in Gogs 0.13.3 and earlier allows remote authenticated users to take over 2FA-protected accounts. The UseRecoveryCode database query selects any unused code by value and usage state without constraining user_id, then marks the matched record used. The attacker must know the victim's username and password and possess any unused recovery code, including one issued to the attacker's own account.
Summary
What happened
Authentication bypass in Gogs 0.13.3 and earlier allows remote authenticated users to take over 2FA-protected accounts. The UseRecoveryCode database query selects any unused code by value and usage state without constraining user_id, then marks the matched record used. The attacker must know the victim's username and password and possess any unused recovery code, including one issued to the attacker's own account.
The record
- CVE
- CVE-2025-64175
- Published
- Feb 6, 2026
- Updated
- Feb 6, 2026
- Vendor
- Gogs
- Product
- Gogs
- Classifications
- CWE-287, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2026CVE publishedPublication date reported by the CVE source.
- Feb 6, 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.13.4
- Affected versionversion=< 0.14.0+dev
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
No public exploit references are available in this record.
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