cve.bz

CVE-2025-8110 Gogs Path Traversal Vulnerability

8.7 highKEVExploit referenceEPSS 80%Fix available

High (8.7) in Gogs Gogs. In CISA KEV since 2026-01-12. EPSS 80% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 4.0

8.7 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/AU:Y/R:U/V:C

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
80% (unchanged from 80% a week ago; 85% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-01-12, due 2026-02-02
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-01-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-8110 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-8110?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-8110?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-8110 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
gogs:gogsthrough 0.13.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mq8m-42gh-wq7rGogogs.io/gogs<=0.13.3no fix published
GO-2025-4225Gogogs.io/gogsall versionsno fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20251230T014957-150000.1.134.1SUSE-SU-2026:0037-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • zAbuQasem/gogs-CVE-2025-8110 Harbor Check: matches CVE 30 stars, Python, created
    CVE-2025-8110 PoC
  • joaquinrrr/CVE-2025-8110 Harbor Check: matches CVE 5 stars, Python, created
    PoC exploit for CVE-2025-8110
  • Ghxstsec/CVE-2025-8110 Harbor Check: matches CVE 5 stars, Python, created
    PoC for CVE-2025-8110 — authenticated RCE in Gogs via symlink bypass in PutContents API (Metasploit PR #22115)
  • Shirouuu/CVE-2025-8110-gogs-poc Harbor Check: matches CVE 4 stars, Python, created
    PoC for CVE-2025-8110 - Gogs arbitrary file write via symlink
  • kayl22/cve-2025-8110-GOGS-RCE Harbor Check: matches CVE 4 stars, Python, created
    GOGS RCE cve-2025-8110 python script that automates the whole attack chain of creating a repository with a symlink file pointing to .git/co…
20 more

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON