CVE-2025-8110
CVE-2025-8110 is a security flaw in Gogs. Attackers can run their own code on Gogs. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 12 Jan 2026.[1]
Gogs is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff.
Description
CISA calls it a path traversal in Gogs Gogs. In its words: “Gogs contains a path traversal vulnerability affecting improper Symbolic link handling in the PutContents API that could allow for code execution.”[1]
The underlying weakness is path traversal (CWE-22), in MITRE’s list of common software weaknesses.[2]
It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it. CISA names the product as Gogs Gogs.
Most families won’t have Gogs; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 12 Jan 2026, 33 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 2 Feb 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 85%. That’s in the top 1% of the flaws it scores.[3]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
CISA’s required action: “Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”[1]
- Check whether you use it.Gogs is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 2 Feb 2026 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 85%.[3] |
See also
Other path traversal flaws
- CVE-2025-61624, Fortinet products: path traversal ·
- CVE-2021-3199, ONLYOFFICE Docs: server path traversal ·
- CVE-2026-104286, Fortinet FortiMail: path traversal ·
- CVE-2026-93616, Check Point products: path traversal ·
- CVE-2026-66384, JFrog Artifactory: improper limitation of a pathname to a restricted directory ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “Gogs Path Traversal Vulnerability”. Known Exploited Vulnerabilities Catalog, added 12 Jan 2026.
- ^ National Institute of Standards and Technology. “CVE-2025-8110 Detail”. National Vulnerability Database, published 10 Dec 2025.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.852, percentile 99.7, 31 Oct 2026.
- CVE Program. “CVE-2025-8110”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.