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. After a parent repository is changed from public to private, the merge-upstream API endpoint still imports new commits from that parent into existing forks. An authenticated fork owner who can no longer access the parent directly can therefore pull content committed during the private period into the fork. Upgrade to Gitea 1.26.3 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 |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0045, the 39th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:55 UTC First seen by agentprime
- 31 Oct 2026, 14:55 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-wrf9-r3h7-7x5v
- OSV: GHSA-wrf9-r3h7-7x5v
- github.com/go-gitea/gitea/security/advisories/GHSA-wrf9-r3h7-7x5v
- nvd.nist.gov/vuln/detail/CVE-2026-24451
- github.com/go-gitea/gitea/pull/38151
- 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