Gitea push mirror API bypass of DISABLE_NEW_PUSH policy
The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUSH` setting that the web interface enforces. A repository administrator could therefore create new push mirrors on instances where the site administrator had disabled them. A push mirror pushes all refs of the repository to a remote chosen by the caller, on each commit or on a schedule.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-97208US | —OT elevated | — | ||
The Gitea API endpoint for creating push mirrors (`POST /api/v1/repos/{owner}/{repo}/push_mirrors`) checked only whether mirroring was enabled and not the `[mirror] DISABLE_NEW_PUS… | ||||
02
references
External citations — patches, advisories, analysis.
- https://blog.gitea.com/release-of-28.1.0/ARTICLE
- https://github.com/go-gitea/gitea/pull/39501FIX
- https://github.com/go-gitea/gitea/pull/39507FIX
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0ARTICLE
- https://github.com/go-gitea/gitea/security/advisories/GHSA-8hhh-mqpg-jpxcADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2026-97208WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan