Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Gitea | Gitea | <= 1.27.3 |
References
- https://blog.gitea.com/release-of-28.0.0/Release Notes
- https://github.com/go-gitea/gitea/pull/39010Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39426Patch, Issue Tracking
- https://github.com/go-gitea/gitea/releases/tag/v28.0.0Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-hcgw-r9gf-8mphVendor Advisory
Timeline
- Published
- Oct 6, 2026
- Last modified
- Oct 13, 2026
- NVD status
- Analyzed