Gogs 0-Day Vulnerability Exploited in the Wild to Hack 700+ Instances
A critical zero-day vulnerability, designated as CVE-2025-8110, has been identified in Gogs, a self-hosted Git service. This vulnerability enables authenticated users to execute a symlink bypass, leading to Remote Code Execution (RCE). Currently, no…
A critical zero-day vulnerability, designated as CVE-2025-8110, has been identified in Gogs, a self-hosted Git service. This vulnerability enables authenticated users to execute a symlink bypass, leading to Remote Code Execution (RCE). Currently, no patch is available, and over 50% of public-facing Gogs instances are estimated to be compromised.
The vulnerability was discovered on Tue, Jul 10, 2025, during an investigation of a malware infection. Analysts identified that threat actors were exploiting a regression in the Gogs API to bypass protections for CVE-2024-55947. The issue stems from Gogs' handling of file modifications via its API, particularly the failure to validate the destination of symlinks. Attackers can commit symlinks that point to sensitive files outside the repository and use the PutContents API to write data, resulting in RCE.
The exploitation requires an account with repository creation privileges. Due to many Gogs instances having open registration, the attack surface is extensive. Approximately 1,400 public-facing Gogs instances have shown signs of compromise, with over 700 confirmed affected. The attacks are characterized by the creation of repositories with random names and the delivery of a payload using Supershell, a Command and Control (C2) framework.
Vulnerability Summary and Indicators of Compromise (IoCs)
Feature Details
Zero-Day CVE CVE-2025-8110 (Symlink Bypass)
A critical zero-day vulnerability, designated as CVE-2025-8110, has been identified in Gogs, a self-hosted Git service.
Related CVE CVE-2024-55947 (Original RCE)
Affected Software Gogs (Self-Hosted Git Service)
Affected Versions v0.13.3 and prior
Status Unpatched (Active Exploitation)
C2 IP Address 119.45.176[.]196, 106.53.108[.]81, 119.91.42[.]53
Administrators of Gogs instances are advised to assume compromise if their instance is exposed to the internet with open registration. Immediate steps include disabling "Open Registration" and restricting service access through VPN or IP allow-lists. Additionally, security teams should scan for unexpected repositories or unusual usage of the PutContents API.
Based on reporting by Cyber Security News.
