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-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
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.
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.
joaquinrrr/CVE-2025-8110Harbor Check: matches CVE5 stars, Python, created PoC exploit for CVE-2025-8110
Ghxstsec/CVE-2025-8110Harbor Check: matches CVE5 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-pocHarbor Check: matches CVE4 stars, Python, created PoC for CVE-2025-8110 - Gogs arbitrary file write via symlink
kayl22/cve-2025-8110-GOGS-RCEHarbor Check: matches CVE4 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
3jee/CVE-2025-8110Harbor Check: matches CVE2 stars, Python, created CVE-2025-8110 — Gogs <= 0.13.3 Arbitrary File Write via Symlink Traversal in PutContents API
kur0bai/CVE-2025-8110Harbor Check: matches CVE1 star, Python, created Automated exploit PoC for CVE-2025-8110 (Gogs Symlink RCE). For educational research and authorized testing only.
ixZODiAK/CVE-2025-8110Harbor Check: matches CVE1 star, Python, created Gogs service Exploit and get the root user
0dgt/CVE-2025-8110Harbor Check: matches CVE1 star, Python, created RCE exploit for Gogs <= 0.13.3
godylockz/CVE-2025-8110Harbor Check: matches CVE0 stars, Python, created Proof of concept for CVE-2025-8110: Gogs authenticated symlink write
r3vpwnx/CVE-2025-8110Harbor Check: matches CVE0 stars, Python, created CVE-2025-8110 - Gogs <=0.13.x symlink bypass -> arbitrary file write as the Gogs process user
9xh4kv/CVE-2025-8110Harbor Check: matches CVE0 stars, Shell, created PoC for CVE-2025-8110: Authenticated RCE in Gogs via symlink bypass in PutContents API
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.