dbcve.org
CWE-23Weakness · CWE-23

CVE-2026-52813

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-24
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.3, organization names containing path traversal sequences (../) are accepted by Gogs, and repositories under them are written to paths following these path traversals. This allows storing/retrieving data for repositories at arbitrary locations on the filesystem. By creating nested structure of Git repositories, one can overwrite the other's hooks configuration to result in Remote Code Execution (RCE). This vulnerability is fixed in 0.14.3.

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 prior to 0.14.3 accepts organization names containing path traversal sequences (../), allowing repositories to be written to arbitrary filesystem locations outside the intended directory. Attackers can exploit this by creating nested repository structures to overwrite hooks configuration and achieve Remote Code Execution.

MitigationUpgrade Gogs to version 0.14.3 or later to patch the path traversal vulnerability in organization name validation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Locate Gogs binary and determine version
    Find the Gogs executable (common locations: /usr/bin/gogs, /opt/gogs/gogs, or run `which gogs`). Run `gogs --version` or check the admin dashboard under 'Site Administration' for the version number.
    Affected if The installed version is less than 0.14.3 (e.g., 0.14.2, 0.14.1, 0.14.0, or any version prior to 0.14.3).
  2. Check if user registration is enabled
    Examine the Gogs configuration file (custom/conf/app.ini) for the setting `Service -> EnableRegister` or check in the admin dashboard under 'Site Settings' -> 'Basic Settings'.
    Affected if User registration is enabled (`ENABLE_REGISTER = true`), allowing any external attacker to register an account and create organizations.
  3. Check if non-admin users can create organizations
    In the admin dashboard, go to 'Site Settings' -> 'Basic Settings' and verify the 'Allow users to create organizations' option. Alternatively, check the configuration file for `Service -> EnableOrgCreation`.
    Affected if Non-admin users are permitted to create organizations (`ENABLE_ORG_CREATION = true`), giving attackers the ability to craft malicious organization names.
  4. Verify path traversal in organization names is blocked
    Attempt to create a test organization with a name containing `../` (e.g., name it `test../org`) using the web interface or API. Observe whether Gogs accepts or rejects the path traversal sequence.
    Affected if Gogs accepts organization names containing `../` path traversal sequences, indicating the vulnerability is present and unpatched.

You are affected if Gogs version is below 0.14.3 AND user registration or organization creation is enabled, allowing attackers to inject path traversal sequences in organization names to write to arbitrary filesystem locations.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Gogs to version 0.14.3 or later to patch the path traversal vulnerability in organization name validation.

Recommended fix High confidence

Gogs 0.14.3

  1. 1. Backup your current Gogs installation and data directory before upgrading.
  2. 2. Download Gogs version 0.14.3 from the official GitHub repository (https://github.com/gogs/gogs/releases).
  3. 3. Stop the running Gogs service.
  4. 4. Replace the existing Gogs binary with the new version 0.14.3 binary.
  5. 5. Review and ensure the gogs/conf/app.ini configuration file is intact.
  6. 6. Start the Gogs service.
  7. 7. Verify that the upgrade was successful by checking the Gogs admin panel for the correct version number.
  8. 8. Test that organization creation now properly rejects path traversal sequences like '../' in organization names.
Caveat Review release notes for any configuration changes between your current version and 0.14.3; minor version upgrades typically have low breaking change risk.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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