CISA Warns of Gogs Path Traversal Vulnerability Exploited in Attacks
A critical path traversal vulnerability in Gogs, a self-hosted Git service, has been identified and is currently being exploited. This vulnerability, known as CVE-2025-8110, was added to the CISA's Known Exploited Vulnerabilities (KEV) catalog on January…
A critical path traversal vulnerability in Gogs, a self-hosted Git service, has been identified and is currently being exploited. This vulnerability, known as CVE-2025-8110, was added to the CISA's Known Exploited Vulnerabilities (KEV) catalog on January 12, 2026, indicating active exploitation by threat actors.
CVE ID CVE-2025-8110
Vulnerability Type Path Traversal – Improper Symbolic Link Handling
Related CWE CWE-22
Impact Code Execution
A critical path traversal vulnerability in Gogs, a self-hosted Git service, has been identified and is currently being exploited.
The CVE-2025-8110 vulnerability affects the Gogs platform due to improper symbolic link handling within the PutContents API. This flaw can allow attackers to escape restricted directories and execute arbitrary code on affected systems.
Path traversal vulnerabilities occur when attackers use specific elements, such as "../" sequences, to navigate outside the intended directories, potentially accessing sensitive files or executing malicious code. In the case of Gogs, this flaw in symbolic link handling enables attackers to manipulate file paths, leading to code execution.
Operational Impact and Recommendations
The inclusion of CVE-2025-8110 in the KEV catalog signifies that this vulnerability is being exploited in real-world attacks. Although it is currently unknown if the vulnerability is being used in ransomware campaigns, its potential for code execution poses a severe security risk for organizations using impacted Gogs installations.
Federal agencies must address this vulnerability by February 2, 2026, as mandated by Binding Operational Directive (BOD) 22-01. Organizations are strongly advised to apply vendor-supplied patches and mitigations immediately. For cloud service deployments, administrators should adhere to the guidance provided in BOD 22-01.
If mitigations are not available, it is recommended to discontinue the use of the vulnerable product.
Based on reporting by Cyber Security News.
