Threats / Gogs / CVE-2025-8110
CVE-2025-8110
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Gogs vulnerability
Gogs contains a path traversal vulnerability in the PutContents API due to improper symbolic link handling, potentially enabling code execution.
Verdict
Today item — known-exploited.
A path traversal flaw in Gogs allows attackers to bypass directory restrictions via symbolic links in the PutContents API, potentially leading to arbitrary code execution on affected systems.
CISA KEV Yes · 2026-01-125EPSS 0.82482 (verify live)6Exploit Weaponized · public PoC7CVSS 8.73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-01-12).
Probability (EPSS)
EPSS 0.82482 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.7 (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/AU:Y/R:U/V:C) · Affected: Gogs, Gogs. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 33 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request to the PutContents API that includes a symbolic link pointing outside the intended directory.
Business
An attacker gains the ability to write files to arbitrary locations on the server.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I place executable code or configuration files in sensitive directories by traversing the filesystem via the symbolic link.
Business
The organization's code repository and server integrity are compromised through unauthorized file placement.
3
Lateral reach — past segmentation narrative 3
Attacker
I trigger execution of the planted code through normal application workflows or direct invocation.
Business
The attacker achieves remote code execution, gaining full control over the Gogs instance and potentially the underlying server.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05