# Gogs: Cross-repository LFS object overwrite via missing content hash verification

Advisory record · `GHSA-cj4v-437j-jq4c`

- **Identifiers:** `GHSA-cj4v-437j-jq4c` · `CVE-2026-25921` · `GO-2026-4616`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html)
- **Tags:** [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 5 Mar 2026
- **Updated:** 23 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Mar 2026, 19:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `gogs.io/gogs` (Go): affected `<0.14.2`; fixed in `0.14.2`

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

Written 7 Nov 2026.

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

- 9.3 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L`, from 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](https://osv.dev/vulnerability/GHSA-cj4v-437j-jq4c)

## Sources

- [GitHub Advisory Database: GHSA-cj4v-437j-jq4c](https://github.com/advisories/GHSA-cj4v-437j-jq4c)
- [OSV: GHSA-cj4v-437j-jq4c](https://osv.dev/vulnerability/GHSA-cj4v-437j-jq4c)
- <https://github.com/gogs/gogs/security/advisories/GHSA-cj4v-437j-jq4c>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-25921>
- <https://github.com/gogs/gogs/pull/8166>
- <https://github.com/gogs/gogs/commit/81ee8836445ac888d99da8b652be7d5cbc5c4d5c>
- <https://github.com/gogs/gogs>
- <https://github.com/gogs/gogs/releases/tag/v0.14.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-cj4v-437j-jq4c>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-cj4v-437j-jq4c/>. Everything for agents: <https://agentprime.io/llms.txt>.