dbcve.org
GogsApplication

CVE-2025-64175

HIGH · 8.8 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 0.13.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Gogs is an open source self-hosted Git service. In version 0.13.3 and prior, Gogs’ 2FA recovery code validation does not scope codes by user, enabling cross-account bypass. If an attacker knows a victim’s username and password, they can use any unused recovery code (e.g., from their own account) to bypass the victim’s 2FA. This enables full account takeover and renders 2FA ineffective in all environments where it's enabled.. This issue has been patched in versions 0.13.4 and 0.14.0+dev.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Gogs 0.13.3 and prior contains an authentication bypass where 2FA recovery code validation fails to scope codes to the specific user account. An attacker with a victim's username/password can use any valid, unused recovery code (from any account) to bypass the victim's 2FA, achieving full account takeover.

MitigationUpgrade Gogs to version 0.13.4 or 0.14.0+dev to patch the vulnerable recovery code validation logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GogsApplication
Affected:< 0.13.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Gogs installation
    Check if Gogs is installed by looking for the gogs binary in common paths (/usr/bin/gogs, /opt/gogs/gogs) or running 'which gogs'. Also check for running processes named 'gogs'.
    Affected if Gogs is not found in the environment, this CVE does not apply.
  2. Determine installed Gogs version
    Run 'gogs --version' or check the version file typically located at /opt/gogs/VERSION or within the gogs binary directory. Compare the version number to 0.13.4.
    Affected if The installed version is 0.13.3 or any version prior to 0.13.4.
  3. Check if 2FA is enabled
    Examine the Gogs database (SQLite, MySQL, or PostgreSQL depending on configuration) in the user table for the 'two_factor_enabled' or 'recovery_codes' field. Alternatively, check the gogs/conf/app.ini configuration file for 2FA-related settings.
    Affected if 2FA is not enabled for any users, the vulnerability cannot be exploited against those accounts.
  4. Verify recovery codes exist
    In the Gogs database, check the user table for the presence of stored recovery codes in the field that stores 2FA recovery codes. These are typically stored as hashed values.
    Affected if No recovery codes exist in the system (no users have set up 2FA with recovery codes), the specific bypass vector does not apply.

You are affected if Gogs version is below 0.13.4 AND 2FA is enabled with recovery codes configured for at least one user.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.13.4 or later
Fixed in 0.13.4
Interim mitigation

Upgrade Gogs to version 0.13.4 or 0.14.0+dev to patch the vulnerable recovery code validation logic.

Recommended fix High confidence

0.13.4 (or 0.14.0+dev for development version)

  1. Backup your current Gogs installation and database
  2. Download Gogs version 0.13.4 or later from the official repository (e.g., https://github.com/gogs/gogs/releases)
  3. Stop the Gogs service
  4. Replace the existing Gogs binary with the new version
  5. Review release notes for any configuration changes required
  6. Start the Gogs service
  7. Verify that 2FA functionality is working correctly after the upgrade
Caveat Review Gogs release notes for version 0.13.4 to check for any configuration or migration changes that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gogs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64175 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64175 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data