Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gogs versions before 0.14.2 are affected. Gogs stores all LFS objects in one shared location without isolating them by repository and does not check uploaded content against its claimed SHA-256 hash, so an authenticated user can overwrite an LFS object belonging to another repository with malicious content. Upgrade to Gogs 0.14.2 or later. The source gives no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.3 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0037, the 31st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:09 UTC First seen by agentprime
- 31 Oct 2026, 15:09 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-cj4v-437j-jq4c
- OSV: GHSA-cj4v-437j-jq4c
- github.com/gogs/gogs/security/advisories/GHSA-cj4v-437j-jq4c
- nvd.nist.gov/vuln/detail/CVE-2026-25921
- github.com/gogs/gogs/pull/8166
- github.com/gogs/gogs/commit/81ee8836445ac888d99da8b652be7d5cbc5c4d5c
- github.com/gogs/gogs
- github.com/gogs/gogs/releases/tag/v0.14.2