Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.26.3 are affected. An authenticated user with Code write access to one repository, and only non-Code access (such as Issues access) to a private source repository, may be able to associate an existing Git LFS object from that source repository with their own repository. If the reused object then becomes downloadable through the target repository, this can expose private LFS content. Upgrade to Gitea 1.26.3 or later.
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 |
|---|---|---|---|---|
| 7.1 | High | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N | CNA (Gitea) |
- CISA KEV Not listed.
- EPSS 0.0032, the 25th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:58 UTC First seen by agentprime
- 31 Oct 2026, 14:58 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-2m9v-5q2g-58vq
- OSV: GHSA-2m9v-5q2g-58vq
- github.com/go-gitea/gitea/security/advisories/GHSA-2m9v-5q2g-58vq
- nvd.nist.gov/vuln/detail/CVE-2026-28740
- github.com/go-gitea/gitea/pull/38050
- github.com/go-gitea/gitea/commit/1c7b7ea72df7cf81e88b8e09049608254d32e56e
- github.com/go-gitea/gitea/commit/7b4a1a1a118501b9d0260301dfed7f52dfc36ee9
- blog.gitea.com/release-of-1.26.3-and-1.26.4
- github.com/go-gitea/gitea
- github.com/go-gitea/gitea/releases/tag/v1.26.3