dbcve.org
GogsApplication

CVE-2024-56731

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 0.13.3 or later.
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 version 0.13.3, it's still possible to delete files under the .git directory and achieve remote command execution due to an insufficient patch for CVE-2024-39931. Unprivileged user accounts can execute arbitrary commands on the Gogs instance with the privileges of the account specified by RUN_USER in the configuration. Allowing attackers to access and alter any users' code hosted on the same instance. This issue has been patched in version 0.13.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 versions before 0.13.3 contain a command injection vulnerability where unprivileged users can delete files under the .git directory, leading to remote command execution with the privileges of the RUN_USER account. This stems from an insufficient patch for CVE-2024-39931, allowing attackers to compromise the entire Gogs instance and access/modify any hosted code.

MitigationImmediately upgrade Gogs to version 0.13.3 or later to patch this vulnerability. Review the RUN_USER configuration and monitor for any unauthorized access or changes to repositories.

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.3

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. Identify installed Gogs version
    Run 'gogs --version' or check the Gogs admin dashboard under 'Site Administration > System Info' to find the exact version number
    Affected if The installed version is anything less than 0.13.3 (for example, 0.13.0, 0.13.1, 0.13.2, or any version 0.12.x)
  2. Verify Gogs configuration file location
    Locate the custom/conf/app.ini configuration file typically found in the Gogs data or installation directory
    Affected if The configuration file exists and Gogs is running from this setup
  3. Check RUN_USER configuration setting
    In the app.ini file, locate the [server] section and find the RUN_USER setting to identify which system user account Gogs operates under
    Affected if RUN_USER is set to a privileged account (such as root) rather than a dedicated low-privilege service account, increasing the impact of successful exploitation
  4. Confirm user registration and repository creation settings
    In app.ini under [service], check if REGISTER_EMAIL_CONFIRM, ENABLE_NOTIFY_MAIL, and ALLOW_EXTERNAL_REGISTRATION are configured, and verify if untrusted users can create repositories
    Affected if User registration is open or untrusted users have the ability to create repositories, allowing them to access the vulnerable functionality

You are affected if Gogs version is below 0.13.3 and your instance permits untrusted or unprivileged users to create accounts or access repositories, as they can exploit the .git directory file deletion to achieve command execution with RUN_USER privileges.

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.3 or later
Fixed in 0.13.3
Vendor patch github.com →
Interim mitigation

Immediately upgrade Gogs to version 0.13.3 or later to patch this vulnerability. Review the RUN_USER configuration and monitor for any unauthorized access or changes to repositories.

Recommended fix High confidence

Gogs 0.13.3

  1. Back up your Gogs data directory (usually /home/gogs/gogs) and database
  2. Download Gogs version 0.13.3 from the official releases: https://github.com/gogs/gogs/releases/tag/v0.13.3
  3. Stop the Gogs service
  4. Replace the existing Gogs binary with the new version 0.13.3 binary
  5. Ensure file permissions match the RUN_USER configured in your gogs/conf/app.ini
  6. Start the Gogs service
  7. Verify the upgrade was successful by checking the Gogs version in the admin panel or via API

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

Fix this in Gogs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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