Gogs cross-account 2FA recovery code authentication bypass
In Gogs (open-source self-hosted Git service) versions 0.13.3 and earlier, two-factor authentication (2FA) recovery code validation is not properly scoped to the authenticating user account. As a result, if an attacker knows a victim’s username and password, they can bypass the victim’s 2FA by supplying any unused recovery code (including a recovery code generated for the attacker’s own account). This breaks the intended binding between recovery codes and the user identity being authenticated, rendering 2FA ineffective for affected deployments. The issue is fixed in Gogs 0.13.4 and 0.14.0+dev.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
Unknown
A security bypass affecting two-factor authentication (2FA) in GOGS.
A Gogs authentication flaw where 2FA recovery codes are not properly bound to the correct user, enabling a cross-account 2FA recovery-code bypass and resulting in account takeover when credentials are known.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.