AI Science Tracker

Gogs recovery-code validation permits cross-account two-factor bypass

Gogs · AI involvement attributed to GPT-5

Finding and attribution

Gogs recovery-code validation ignored the authenticating user ID and searched globally for any unused code. An attacker who already knows a victim’s username and password could enter an unused recovery code from the attacker’s own account during the victim’s login, bypassing the victim’s second factor and logging in as that victim.

Product: Gogs. AI system: GPT-5. Team / organization: OpenAI Security Research / Gogs maintainers.

CVE identifiers: CVE-2025-64175.

AI and human contribution (source account): The Gogs advisory embeds an OpenAI Security Research report naming OpenAI as discoverer and gives the case-specific timeline “Discovered via GPT5” followed by PoC reproduction and confirmation. The report does not establish autonomous discovery or a more detailed model workflow.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The public maintainer advisory was published 2026-02-06. The report documents PoC reproduction; it does not report exploitation in the wild or establish whether defenders knew of the flaw before discovery.

Remediation status: fix documented. The upstream commit scopes the recovery-code query to the authenticating user and marks that user’s code used. The maintainer advisory lists versions >=0.11.19 and <=0.13.3 as affected and 0.13.4 as patched.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 6 Feb 2026. AI attribution dated 6 Feb 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: authentication bypass.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

No source-backed CVSS assessment is established in this catalog.

CVE-2025-64175: authentication bypass.
Prerequisites / affected scope: Attacker must already know the victim’s username and password, and the victim account must have two-factor authentication enabled. An unused recovery code belonging to another account can then complete the victim’s login..
Exploitation evidence: The embedded report describes a reproduced proof of concept; it does not report exploitation in the wild.. Impact source · checked 17 Nov 2026.

Documented fix: The upstream commit scopes the recovery-code query to the authenticating user and marks that user’s code used. The maintainer advisory lists versions >=0.11.19 and <=0.13.3 as affected and 0.13.4 as patched.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases