Is CVE-2025-8110 exploited in the wild?

Yes. CVE-2025-8110 is known to be exploited in the wild, first recorded on 12 January 2026. Treat it as urgent.

How severe is CVE-2025-8110?

Critical severity, with a CVSS score of 8.8, published 10 December 2025.

Which products and versions are affected?

gogs.io/gogs (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=0.13.3; Gogs up to and including 0.13.3.

Is there a fix for CVE-2025-8110?

A patch was published on 2025-12-11: Fix committed to Gogs repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-8110 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2025-8110?

Check whether you run gogs.io/gogs (Go) or Gogs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-8110: Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code.

CVE-2025-8110 · Severity: critical · CVSS 8.8 · Exploited in the wild · Published 2025-12-10

Gogs is a self-hosted Git service used by developers to manage and store source code. A critical vulnerability in its file handling system allows an attacker with basic user permissions to bypass security restrictions and execute malicious code on the server. This could lead to a complete takeover of the service, theft of proprietary source code, or disruption of development operations. This vulnerability is known to be actively exploited in the wild.

Technologies: gogs.io/gogs (Go), Gogs. Vendors: Go, Gogs.

Quick answers

Is CVE-2025-8110 exploited in the wild?: Yes. CVE-2025-8110 is known to be exploited in the wild, first recorded on 12 January 2026. Treat it as urgent.
How severe is CVE-2025-8110?: Critical severity, with a CVSS score of 8.8, published 10 December 2025.
Which products and versions are affected?: gogs.io/gogs (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=0.13.3; Gogs up to and including 0.13.3.
Is there a fix for CVE-2025-8110?: A patch was published on 2025-12-11: Fix committed to Gogs repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-8110 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2025-8110?: Check whether you run gogs.io/gogs (Go) or Gogs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A path traversal vulnerability (CWE-22) exists in Gogs versions up to 0.13.3. The flaw is located in the PutContents API, where improper handling of symbolic links allows an attacker to write files outside of the intended directory. By exploiting this, a remote attacker with low-level authenticated access can achieve arbitrary code execution on the host system. The vulnerability has been observed in active exploitation, and a patch has been released in the Gogs repository. Security researchers have demonstrated that this can lead to full Remote Code Execution (RCE).

Affected products

Gogs Gogs up to and including 0.13.3

Identifiers

CVE-2025-8110
GHSA-mq8m-42gh-wq7r
GO-2025-4225

Timeline

2025-12-10: disclosed: Vulnerability reported by Wiz research
2025-12-11: patched: Fix committed to Gogs repository
2026-01-12: kev added: CISA added to Known Exploited Vulnerabilities catalog

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.