Gitea push mirror SSRF and forced writes to internal Git hosts
Summary
| CVE | CVE-2026-89430 |
|---|---|
| State | PUBLISHED |
| Assigner | Gitea |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-06 20:17:34 UTC |
| Updated | 2026-10-06 20:17:34 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-367 | CWE-918 | CWE-367 CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition | CWE-918 CWE-918: Server-Side Request Forgery (SSRF)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/go-gitea/gitea/releases/tag/v28.0.0 | 88ee5874-cf24-4952-aea0-31affedb7ff2 | github.com | |
| github.com/go-gitea/gitea/security/advisories/GHSA-hcgw-r9gf-8mph | 88ee5874-cf24-4952-aea0-31affedb7ff2 | github.com | |
| github.com/go-gitea/gitea/pull/39010 | 88ee5874-cf24-4952-aea0-31affedb7ff2 | github.com | |
| github.com/go-gitea/gitea/pull/39426 | 88ee5874-cf24-4952-aea0-31affedb7ff2 | github.com | |
| blog.gitea.com/release-of-28.0.0 | 88ee5874-cf24-4952-aea0-31affedb7ff2 | blog.gitea.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: https://github.com/thesmartshadow (en)
CNA: https://github.com/manus-use (en)
CNA: https://github.com/cy3erm (en)
CNA: https://github.com/TheFox0x7 (en)
CNA: https://github.com/silverwind (en)
CNA: https://github.com/bircni (en)
CNA: https://github.com/wxiaoguang (en)
There are currently no legacy QID mappings associated with this CVE.