CVE-2025-8110 | File overwrite in file update API in Gogs

Exp

Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code.

Published: 2025-12-10 Last update: 2026-01-20 Assigner: 9947ef80-c5d5-474a-bbab-97341a59000e Source: 9947ef80-c5d5-474a-bbab-97341a59000e
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-8110 is rated Critical Active Threat (99.6/100): CVSS High severity, with high exploitation likelihood (EPSS 76.94%, 99th percentile). CISA KEV confirms active exploitation (added 2026-01-12) affecting Gogs / Gogs. a weakness (CWE-22) Unauthenticated remote administrative access may be possible. EPSS rose +59.20% over the last day, indicating growing attacker interest. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2025-8110

Name: Gogs Path Traversal Vulnerability · CISA KEV detail

Exploit added: 2026-01-12

Action due: 2026-02-02

Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Public exploit references (Exploit-DB) for CVE-2025-8110

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-8110

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 17.74% 76.94% +59.20%
2 2026-05-30 22.35% 17.74% -4.61%
3 2026-05-28 — 22.35% —

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-8110

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.7 4.0 HIGH
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:X Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:L)
Low privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:H)
High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:H)
High integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N)
No availability impact on subsequent systems.
Exploit maturity (threat) (E:A)
Attacked: exploitation has been reported, or toolkits exist that simplify exploitation.
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:Y)
Yes: all four kill-chain steps (reconnaissance, weaponization, delivery, exploitation) can be automated.
Recovery (supplemental) (R:U)
User: manual user intervention is needed to recover services.
Value density (supplemental) (V:C)
Concentrated: a single exploit event controls rich resources (e.g., a central server).
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — 9947ef80-c5d5-474a-bbab-97341a59000e
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2025-8110

GitHub Security Advisory for CVE-2025-8110

GHSA-mq8m-42gh-wq7r · Severity: high · Ecosystem: go — Gogs vulnerable to a bypass of CVE-2024-55947

OS Trackers for CVE-2025-8110

vendor priority summary link
alpine high CVE-2025-8110: 1 source package rows (gogs); 4 state rows across 1 repos (edge-community); fixed 0, open 4. https://security.alpinelinux.org/vuln/CVE-2025-8110

Affected software / configurations for CVE-2025-8110

Vendor Product Version Raw CPE
gogs gogs <= 0.13.3 cpe:2.3:a:gogs:gogs:*:*:*:*:*:*:*:*

References for CVE-2025-8110

cvelogic Threat Intelligence