CVE-2025-8110
Path Traversal in Gogs ≤ 0.13.3
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:C/RE:X/U:XSummary
CVE-2025-8110 is a high-severity Path Traversal (CWE-22) vulnerability in Gogs Gogs. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-8110 involves improper symbolic link handling in the PutContents API of Gogs, enabling local execution of code. This vulnerability, tied to CWE-22 (Path Traversal), affects Gogs, a self-hosted Git service. Published on 2025-12-10, it carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to network accessibility and significant impact potential.
An attacker requires low privileges (PR:L) to exploit this over the network (AV:N) with low attack complexity (AC:L) and no user interaction (UI:N). Exploitation allows achievement of high confidentiality, integrity, and availability impacts, facilitating local code execution on the affected system.
Mitigation guidance is detailed in referenced advisories, including the Wiz Research blog on the Gogs CVE-2025-8110 RCE exploit (http://wiz.io/blog/wiz-research-gogs-cve-2025-8110-rce-exploit) and OSS-Security mailing list discussions (http://www.openwall.com/lists/oss-security/2025/12/11/3, http://www.openwall.com/lists/oss-security/2025/12/11/4, http://www.openwall.com/lists/oss-security/2026/01/17/4, http://www.openwall.com/lists/oss-security/2026/01/18/1). Security practitioners should review these for patching instructions and workarounds.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-202425
Vulnerability Data
Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code.
- CWE(s)
- KEV Date Added
- 12 January 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.