Description
Gogs is an open source self-hosted Git service. Versions 0.13.4 and below have an access control bypass vulnerability which allows any repository collaborator with Write permissions to delete protected branches (including the default branch) by sending a direct POST request, completely bypassing the branch protection mechanism. This vulnerability in the DeleteBranchPost function eenables privilege escalation from Write to Admin level, allowing low-privilege users to perform dangerous operations that should be restricted to administrators only. Although Git Hook layer correctly prevents protected branch deletion via SSH push, the web interface deletion operation does not trigger Git Hooks, resulting in complete bypass of protection mechanisms. In oder to exploit this vulnerability, attackers must have write permissions to the target repository, protected branches configured to the target repository and access to the Gogs web interface. This issue has been fixed in version 0.14.1.
Published: 2026-02-19
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation via Protected Branch Deletion
Action: Immediate Patch
AI Analysis

Impact

Gogs versions 0.13.4 and older contain a flaw in the DeleteBranchPost handler that allows any repository collaborator with write access to delete protected branches, including the default branch, by sending a direct POST request. The vulnerability bypasses the branch protection mechanism, elevating a write‑level user to administrator level functionality. The exploitation does not involve external code injection or arbitrary code execution; instead it permits unauthorized modification of repository history and deletion of critical branches.

Affected Systems

The vulnerability affects Gogs repositories hosted on the open source Gogs platform. All instances running version 0.13.4 or earlier are susceptible. The fix is available in the 0.14.1 release. Administrators must check their Gogs installation version and update if it falls within the vulnerable range.

Risk and Exploitability

The CVSS base score is 7.1, indicating a high severity vulnerability. The EPSS score is reported as less than 1%, meaning the probability of exploitation is very low but not zero. The vulnerability is not listed in the CISA KEV catalog, suggesting no documented active exploits. An attacker must own write access to a repository that has protected branches and must be able to access the Gogs web interface. When these conditions are met, an exploit can be executed with a single POST request, providing the attacker with privileged abilities normally reserved for administrators.

Generated by OpenCVE AI on April 18, 2026 at 11:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Gogs installation to version 0.14.1 or later, which removes the DeleteBranchPost bypass.
  • Re‑evaluate repository permissions so that only administrators retain delete rights for protected branches, limiting write permissions to collaborators who should not have such power.
  • Monitor web server logs for DeleteBranchPost requests targeting protected branches and investigate any unauthorized attempts.

Generated by OpenCVE AI on April 18, 2026 at 11:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-2c6v-8r3v-gh6p Gogs has a Protected Branch Deletion Bypass in Web Interface
History

Fri, 20 Feb 2026 01:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 19 Feb 2026 19:45:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:gogs:gogs:*:*:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Thu, 19 Feb 2026 10:30:00 +0000

Type Values Removed Values Added
First Time appeared Gogs
Gogs gogs
Vendors & Products Gogs
Gogs gogs

Thu, 19 Feb 2026 03:30:00 +0000

Type Values Removed Values Added
Description Gogs is an open source self-hosted Git service. Versions 0.13.4 and below have an access control bypass vulnerability which allows any repository collaborator with Write permissions to delete protected branches (including the default branch) by sending a direct POST request, completely bypassing the branch protection mechanism. This vulnerability in the DeleteBranchPost function eenables privilege escalation from Write to Admin level, allowing low-privilege users to perform dangerous operations that should be restricted to administrators only. Although Git Hook layer correctly prevents protected branch deletion via SSH push, the web interface deletion operation does not trigger Git Hooks, resulting in complete bypass of protection mechanisms. In oder to exploit this vulnerability, attackers must have write permissions to the target repository, protected branches configured to the target repository and access to the Gogs web interface. This issue has been fixed in version 0.14.1.
Title Gogs has a Protected Branch Deletion Bypass in Web Interface
Weaknesses CWE-863
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-02-19T17:44:52.867Z

Reserved: 2026-01-30T14:44:47.328Z

Link: CVE-2026-25232

cve-icon Vulnrichment

Updated: 2026-02-19T17:04:57.240Z

cve-icon NVD

Status : Analyzed

Published: 2026-02-19T07:17:45.520

Modified: 2026-02-19T19:44:07.857

Link: CVE-2026-25232

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-18T12:00:05Z

Weaknesses