CVE-2025-8110 is a high-severity (CVSS 8.8) Path Traversal vulnerability in gogs.io/gogs. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-01-12) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2025-8110 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Gogs vulnerable to a bypass of CVE-2024-55947
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-01-12. Federal agencies were required to remediate by 2026-02-02.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-8110.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-8110 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 0 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
gogs.io/gogsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | gogs.io/gogs | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
zAbuQasem/gogs-CVE-2025-8110
CVE-2025-8110 PoC
rxerium/CVE-2025-8110
Detection template for CVE-2025-8110
Ghxstsec/CVE-2025-8110
Shirouuu/CVE-2025-8110-gogs-poc
PoC for CVE-2025-8110 - Gogs arbitrary file write via symlink
joaquinrrr/CVE-2025-8110
PoC exploit for CVE-2025-8110
kayl22/cve-2025-8110-GOGS-RCE
GOGS RCE cve-2025-8110 python script that automates the whole attack cha
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gogs.io/gogs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of gogs.io/gogs has shipped for CVE-2025-8110 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-8110 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-8110. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-8110 in your dependencies?
O3 detects CVE-2025-8110 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.