CVE-2026-24451
Gitea 1.26.2 allows fork synchronization to continue after a parent …
Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- blog.gitea.com/release-of-1.26.3-and-1.26.4/
- github.com/go-gitea/gitea/pull/38151
- github.com/go-gitea/gitea/releases/tag/v1.26.3
- github.com/go-gitea/gitea/security/advisories/GHSA-wrf9-r3h7-7x5v
- nvd.nist.gov/vuln/detail/CVE-2026-24451
- blog.gitea.com/release-of-1.26.3-and-1.26.4
- github.com/advisories/GHSA-wrf9-r3h7-7x5v
- nvd.nist.gov/vuln/detail/CVE-2026-24451
- cve.org/CVERecord?id=CVE-2026-24451
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.