dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-52797

HIGH · 8.5 CVSS v3.1 Published 2026-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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. Prior to 0.14.0, as an authorized user, an intruder can dictate the value which is passed to the git diff command which, together with bypassing the filtering of the passed value, allows the user to bypass the target directory and write the result of the comparison to any arbitrary path. This vulnerability is fixed in 0.14.0.

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

This is a path traversal vulnerability in Gogs prior to version 0.14.0 where authenticated users can manipulate input passed to the git diff command, bypassing filtering to write comparison results to arbitrary file system paths instead of the intended target directory.

MitigationUpgrade Gogs to version 0.14.0 or later which contains the patch that properly validates and filters git diff input paths to prevent directory traversal.

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

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
Changed
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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. Confirm Gogs installation and locate binary
    Run 'gogs --version' from the Gogs binary location, or check the admin dashboard under 'Site Administration' for the installed version number.
    Affected if The version shown is below 0.14.0 (e.g., 0.13.x, 0.12.x, etc.)
  2. Verify git diff functionality is accessible
    Log into Gogs as any user and navigate to a repository, then access the comparison view (e.g., compare two branches or commits via the URL pattern /{user}/{repo}/compare/{base}...{head}) or the diff view for a commit.
    Affected if The git diff/comparison feature is available and functional in the Gogs instance.
  3. Check if external user registration or guest access is enabled
    In the Gogs admin panel, go to 'Authentication' and 'Site Settings' to review whether user self-registration is enabled, or if there are any existing user accounts besides the admin.
    Affected if Any non-admin user accounts exist, or self-registration allows new users to register, meaning an attacker could obtain authenticated access.
  4. Review git hook or upload configuration
    Examine the Gogs configuration file (custom/conf/app.ini) for any settings related to repository hooks, git upload, or diff processing that may indicate exposure to the vulnerable code path.
    Affected if The configuration allows standard git operations without additional restrictions on diff parameters.

You are affected if your Gogs version is below 0.14.0 and the git diff/comparison feature is accessible to authenticated users, which is the default configuration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Gogs to version 0.14.0 or later which contains the patch that properly validates and filters git diff input paths to prevent directory traversal.

Recommended fix High confidence

Gogs 0.14.0

  1. 1. Backup your current Gogs installation and data directory before upgrading
  2. 2. Identify your current Gogs version by checking the admin dashboard or running the binary with version flag
  3. 3. Download Gogs version 0.14.0 or later from the official GitHub repository (https://github.com/gogs/gogs/releases)
  4. 4. Stop the Gogs service on your server
  5. 5. Replace the existing Gogs binary with the new version 0.14.0 binary
  6. 6. Ensure file permissions are correctly set on the new binary
  7. 7. Start the Gogs service
  8. 8. Verify the upgrade was successful by checking the admin dashboard shows version 0.14.0 or later
Caveat Review release notes for 0.14.0 to check for any breaking changes in configuration or features

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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