dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-52806

CRITICAL · 9.9 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 Zero-click Patch available 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.3, Gogs allows authenticated users to achieve Remote Code Execution (RCE) on the server by creating a pull request with a specially crafted branch name that injects the --exec flag into the git rebase command during the "Rebase before merging" merge operation. 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 before version 0.14.3 contains a command injection vulnerability where authenticated users can achieve remote code execution by creating a pull request with a specially crafted branch name that injects the --exec flag into the git rebase command during the 'Rebase before merging' merge operation.

MitigationUpgrade Gogs to version 0.14.3 or later to patch the command injection vulnerability that allows authenticated users to achieve RCE via crafted branch names.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Gogs installation
    Check for Gogs binary or service - look for 'gogs' process or binary at common paths like /usr/bin/gogs, /opt/gogs/, or run 'gogs --version' if in PATH
    Affected if Gogs is not installed or this check does not apply
  2. Determine installed Gogs version
    Run 'gogs --version' or check the admin dashboard under '/admin' for the version information, then compare to 0.14.3
    Affected if The installed version is lower than 0.14.3 (e.g., 0.14.2, 0.14.1, 0.14.0, etc.)
  3. Check if Rebase before merging is enabled
    Navigate to repository settings at '/[repo]/settings' or global admin settings at '/admin' and look for merge options - verify if 'Rebase before merging' or similar rebase merge options are enabled
    Affected if The 'Rebase before merging' merge option is enabled in repository or global settings
  4. Verify pull request creation is permitted
    Check repository or global settings under 'Repository' or 'Repository settings' to confirm authenticated users can create pull requests
    Affected if Authenticated users have permission to create pull requests

A user is affected if Gogs version is below 0.14.3 AND the Rebase before merging feature is enabled AND authenticated users can create pull requests in at least one repository.

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 command injection vulnerability that allows authenticated users to achieve RCE via crafted branch names.

Recommended fix High confidence

0.14.3

  1. 1. Backup your current Gogs installation and data directory
  2. 2. Stop the Gogs service
  3. 3. Download Gogs version 0.14.3 from the official repository (github.com/gogs/gogs)
  4. 4. Replace the existing Gogs binary with the new version 0.14.3 binary
  5. 5. Ensure file permissions are correctly set on the new binary
  6. 6. Start the Gogs service
  7. 7. Verify the upgrade was successful by checking the Gogs admin panel or running 'gogs --version'
  8. 8. Test that the 'Rebase before merging' functionality works correctly with a test repository

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 the patch applied

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-52806 — 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-52806 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