Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to `git push`, so a name that later resolved to a blocked or internal address was still reached. A user with administrator access to a repository, which includes repositories they create themselves, could aim push mirror synchronization at internal Git services and force-push the repository's contents to them.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/go-gitea/gitea/pull/39010 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39426 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/security/advisories/GHSA-hcgw-r9gf-8mph Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.1 · giteaNVD modified 2026-10-13 16:46
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 5
- https://blog.gitea.com/release-of-28.0.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39010 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39426 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/releases/tag/v28.0.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-hcgw-r9gf-8mph Vendor Advisory