dbcve.org
GogsApplication

CVE-2025-64111

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 0.13.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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, due to the insufficient patch for CVE-2024-56731, it's still possible to update files in the .git directory and achieve remote command execution. 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 versions 0.13.3 and prior contain a path traversal vulnerability allowing attackers to write files to the .git directory, bypassing an incomplete fix for CVE-2024-56731. This arbitrary file write capability can be leveraged to achieve remote command execution on the server.

MitigationUpgrade Gogs to version 0.13.4 or 0.14.0+dev to apply the complete patch for this vulnerability.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Gogs version
    Log into the Gogs administrative interface and navigate to the admin dashboard or site administration page to view the running version. Alternatively, check the binary version using 'gogs --version' or inspect the version displayed on the login page footer.
    Affected if The displayed version is 0.13.3 or any version prior to 0.13.4 (e.g., 0.13.2, 0.13.1, 0.13.0, 0.12, etc.)
  2. Confirm web interface is accessible
    Verify that the Gogs web interface is reachable over HTTP/HTTPS. This vulnerability is exploited via HTTP requests to the web application.
    Affected if The Gogs web interface is exposed and accepts external requests (not restricted to localhost only).
  3. Inspect .git repository directory for unexpected files
    Locate the repository storage directory (commonly 'gogs-repositories' or similar in the Gogs data path). Within individual repository directories, examine the .git folder contents for any files that should not exist there, such as new config files, scripts, or binary files that were not created by normal Gits operations.
    Affected if Unexpected files or modifications are found within .git directories that were not created by standard git operations or Gits internal processes.

A user is affected if their Gogs installation shows a version lower than 0.13.4 and has its web interface accessible, as the path traversal vulnerability can be exploited via HTTP requests to write arbitrary files to .git directories.

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 apply the complete patch for this vulnerability.

Recommended fix High confidence

0.13.4 or later (including 0.14.0+dev)

  1. 1. Back up your existing Gogs data directory (usually /home/gogs/gogs or /var/gogs)
  2. 2. Back up your Gogs database if using a database backend
  3. 3. Stop the Gogs service (e.g., systemctl stop gogs or equivalent)
  4. 4. Download the latest Gogs release from https://github.com/gogs/gogs/releases (version 0.13.4 or later)
  5. 5. Extract the new binary and replace the existing gogs binary
  6. 6. Ensure file permissions are correct (executable by gogs user)
  7. 7. Start the Gogs service (e.g., systemctl start gogs)
  8. 8. Verify the upgrade by logging into Gogs and checking the version in the admin panel

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64111 — 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-64111 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