ZeroHour
Security Affairspublished ()ingested @securityaffairs

U.S. CISA adds a flaw in Gogs to its Known Exploited Vulnerabilities catalog

highExploit / PoC exploited in the wildimportance 60CVE-2025-8110CVE-2024-55947

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2024-55947
Path Traversal File Write in Gogs Enables SSH Access (Actively Exploited)

CVE-2024-55947 is a path traversal flaw (CWE-22) in Gogs, an open source self-hosted Git service, that allows a malicious user to write a file to an arbitrary path on the server. It requires only low privileges, so any authenticated Gogs user can trigger it over the network without user interaction, and by planting a file in a sensitive location — such as the service account's SSH authorized_keys — the attacker gains SSH access to the host, effectively compromising the server (high confidentiality, integrity, and availability impact per CVSS). All Gogs deployments running versions prior to 0.13.1 are affected. Exploitation is no longer theoretical: recent reporting describes active attacks hitting 700+ instances, and CISA has flagged the flaw as actively exploited, adding it to its Known Exploited Vulnerabilities catalog. EPSS assigns a 75.2% probability of exploitation within 30 days (99th percentile), underscoring elevated risk for exposed instances.

Do: Upgrade all Gogs instances to 0.13.1 or later, which fixes this flaw, and treat the upgrade as urgent given active exploitation and the KEV listing. Check your deployed version, audit the host for rogue SSH keys and unexpected file writes (especially the git service account's authorized_keys), and review account activity and logs for signs of compromise. Until patched, limit network exposure of the Gogs service and the server's SSH port, and restrict account creation to trusted users.

8.775% PoC
  • Gogs (self-hosted Git service) all versions prior to 0.13.1 (fixed in 0.13.1)
moderateseveral thousand internet-exposed Gogs instances, with 700+ confirmed exploited in the current campaign
CVE-2025-8110
Actively Exploited Path Traversal RCE in Gogs (PutContents API)

CVE-2025-8110 is a path-traversal flaw (CWE-22) caused by improper symbolic-link handling in the PutContents API of the self-hosted Git service Gogs. An attacker with low-privileged access to the API can abuse symlinks so that file operations escape the intended directory, resulting in code execution on the server hosting Gogs. Because the attack works over the network with only low privileges and no user interaction, any Gogs deployment whose API is reachable — particularly internet-facing instances — is exposed. This is a zero-day: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-01-12 after reports of active attacks against 700+ instances, and at the time of the KEV listing no official patch was available, though a fix was in progress in Gogs pull request #8078. EPSS assigns an 82.5% probability of exploitation within 30 days (100th percentile), and CISA's required action is to apply vendor mitigations, follow BOD 22-01 guidance for cloud services, or discontinue use if mitigations are unavailable.

Do: Because no official patch was released at the time of the KEV listing, track gogs/gogs PR #8078 and upgrade to the fixed release as soon as it ships; in the interim, follow CISA's required action by applying vendor mitigations or restricting or discontinuing internet exposure of Gogs instances. Reduce attack surface by limiting low-privileged account access to the PutContents/write APIs and firewalling Gogs servers, and hunt for indicators of compromise on any internet-facing Gogs deployment given confirmed attacks against 700+ instances.

8.782% KEV PoC ×3
  • Gogs
moderate≈700+ instances confirmed exploited; the broader population of internet-exposed Gogs deployments is likely in the thousands to tens of thousands (estimate)
Full article443 words · extracted from securityaffairs.com · click to collapse

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) adds a flaw impacting Gogs to its Known Exploited Vulnerabilities catalog.

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added a Gogs path traversal vulnerability, tracked as CVE-2025-8110 (CVSS Score of 8.7), to its Known Exploited Vulnerabilities (KEV) catalog.

Gogs (Go Git Service) is a lightweight, open-source, self-hosted Git service written in Go.

The vulnerability is an improper symbolic link handling in the PutContents API in Gogs that allows local execution of code.

An improper symbolic link is a symlink that is created or handled in an unsafe way, allowing it to point to files or directories outside the intended or permitted scope.

Wiz Research found the vulnerability while probing a malware incident in July, and the flaw was addressed a week later.

“A symlink bypass (CVE-2025-8110) of a previously patched RCE (CVE-2024-55947) allows authenticated users to overwrite files outside the repository, leading to Remote Code Execution (RCE).” reported Wiz Research. “We identified over 700 compromised instances public-facing on the internet.”

The flaw CVE-2025-8110 is a bypass for an earlier RCE vulnerability tracked as CVE-2024-55947), which was originally discovered by ManassehZhou.

Gogs had a previous flaw (CVE-2024-55947) in the PutContents API that let attackers write files outside a repository and run commands. The developers fixed it with path validation, but they didn’t check for symbolic links.

The new bypass (CVE-2025-8110) takes advantage of Git’s symlink feature. An attacker can create a symlink in a repository that points to a file outside the repo, then use the API to write through the symlink. The system follows the link and overwrites the target file, like .git/config, letting the attacker execute commands. This shows a repeated problem with symlink handling in Gogs.

The researchers explained that a malware infection on a customer’s cloud workload revealed a publicly exposed Gogs service. Suspicious repositories with random 8-character names, created shortly before the infection, indicated an automated attack. Expanding the search found approximately 1,400 exposed Gogs instances, with over 700 compromised, all showing the same patterns, suggesting a single actor or group using the same automated tools.

Gogs CISA

According to Binding Operational Directive (BOD) 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities, FCEB agencies have to address the identified vulnerabilities by the due date to protect their networks against attacks exploiting the flaws in the catalog.

Experts also recommend that private organizations review the Catalog and address the vulnerabilities in their infrastructure.

CISA orders federal agencies to fix the vulnerabilities by February 2, 2026.

Pierluigi Paganini

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

(SecurityAffairs – hacking, US CISA Known Exploited Vulnerabilities catalog)



Text extracted automatically; images, tables and formatting may be missing. Original: https://securityaffairs.com/186837/hacking/u-s-cisa-adds-a-flaw-in-gogs-to-its-known-exploited-vulnerabilities-catalog.html