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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 85.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.

🐹 Go

CISA KEV · ACTIVELY EXPLOITED

Gogs vulnerable to a bypass of CVE-2024-55947GHSA-mq8m-42gh-wq7r

Fix: gogs/gogs#8078

GHSA-mq8m-42gh-wq7r is a 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. No vendor fix is recorded yet; mitigation options are listed below.

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

Published

Dec 10, 2025

Updated

Feb 3, 2026

Affected

1 pkg

Patched

See advisory

Exploits

6 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

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 GHSA-mq8m-42gh-wq7r.

EPSS Exploitation Probability

via FIRST.org ↗

85.2%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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

Affected Products

1 product · 1 configurations

Application

gogsgogs

≤ 0.13.3

range

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

⭐ 31🍴 0Sep 2026

rxerium/CVE-2025-8110

Detection template for CVE-2025-8110

⭐ 22🍴 0Jul 2026

Ghxstsec/CVE-2025-8110

⭐ 5🍴 3Aug 2026

joaquinrrr/CVE-2025-8110

PoC exploit for CVE-2025-8110

⭐ 5🍴 0Jun 2026

kayl22/cve-2025-8110-GOGS-RCE

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

⭐ 4🍴 0Jun 2026

Shirouuu/CVE-2025-8110-gogs-poc

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

⭐ 4🍴 0Sep 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How to detect GHSA-mq8m-42gh-wq7r

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-mq8m-42gh-wq7r -u https://target

Template: Gogs <= 0.13.3 - Remote Code Execution
Severity: high
Impact: Local attackers can execute arbitrary code, potentially leading to full system compromise.
Remediation: Update to the latest version of Gogs.

Template by ProjectDiscovery nuclei-templates (rxerium), MIT licensed. View the full template. Scan only systems you are authorised to test.

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?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works