How severe is GHSA-mq8m-42gh-wq7r?

No CVSS score has been assigned to GHSA-mq8m-42gh-wq7r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mq8m-42gh-wq7r?

GHSA-mq8m-42gh-wq7r affects the following packages: gogs.io/gogs (Go). Ecosystems affected: Go.

How do I fix GHSA-mq8m-42gh-wq7r?

No patched version of gogs.io/gogs has shipped for GHSA-mq8m-42gh-wq7r yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-mq8m-42gh-wq7r in my Go dependencies?

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.

How do I mitigate GHSA-mq8m-42gh-wq7r if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-mq8m-42gh-wq7r?

O3 pinpoints whether GHSA-mq8m-42gh-wq7r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mq8m-42gh-wq7r actively exploited in the wild?

Yes. There are 6 known exploit references for GHSA-mq8m-42gh-wq7r, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-mq8m-42gh-wq7r?

GHSA-mq8m-42gh-wq7r has an EPSS (Exploit Prediction Scoring System) score of 82.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-mq8m-42gh-wq7r in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-mq8m-42gh-wq7r (Gogs Path Traversal Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-01-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-02-02. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-mq8m-42gh-wq7r?

GHSA-mq8m-42gh-wq7r is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-mq8m-42gh-wq7r?

A Nuclei detection template exists for GHSA-mq8m-42gh-wq7r, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-mq8m-42gh-wq7r published, and has it been updated?

GHSA-mq8m-42gh-wq7r was published on December 10, 2025 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-01-12 — agencies required to remediate by 2026-02-02

🐹 Go

GHSA-mq8m-42gh-wq7r

Gogs vulnerable to a bypass of CVE-2024-55947

Also known asCVE-2025-8110GO-2025-4225

Published

Dec 10, 2025

Updated

Feb 3, 2026

Affected

1 pkg

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

82.2%probability of exploitation in next 30 days

Very High Risk100th percentile+5.61%

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.

Blast Radius

1 pkg affected

🐹gogs.io/gogs

Real-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

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`gogs.io/gogs`	all versions	No fix

Exploits & PoCs

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

⭐ 28🍴 0Jul 2026

rxerium/CVE-2025-8110

Detection template for CVE-2025-8110

⭐ 22🍴 0Jul 2026

joaquinrrr/CVE-2025-8110

PoC exploit for CVE-2025-8110

⭐ 5🍴 0Jun 2026

Shirouuu/CVE-2025-8110-gogs-poc

PoC for CVE-2025-8110 - Gogs arbitrary file write via symlink

⭐ 5🍴 0Jul 2026

kayl22/cve-2025-8110-GOGS-RCE

GOGS RCE cve-2025-8110 python script that automates the whole attack cha

⭐ 4🍴 0Jun 2026

Ghxstsec/CVE-2025-8110

⭐ 3🍴 3Jul 2026

Detection & mitigation playbook

Open-source dependency

Detect
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 GHSA-mq8m-42gh-wq7r 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 GHSA-mq8m-42gh-wq7r 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 GHSA-mq8m-42gh-wq7r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-mq8m-42gh-wq7r in your dependencies?

O3 detects GHSA-mq8m-42gh-wq7r across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-mq8m-42gh-wq7r

EPSS Exploitation Probability

Blast Radius

Description

Affected Packages

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is GHSA-mq8m-42gh-wq7r in your dependencies?