CVE-2026-97208: Gitea push mirror API bypass of DISABLE_NEW_PUSH policy

Published Oct 6, 2026
·
Updated

The Gitea API endpoint for creating push mirrors (POST /api/v1/repos/{owner}/{repo}/pushmirrors) checked only whether mirroring was enabled and not the [mirror] DISABLENEWPUSH 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.

Affected Software

1 affected component
Gitea Gitea

Event History

Oct 6, 2026
CVE Published
via MITRE·09:17 PM
Data Sourced
via MITRE·09:17 PM
DescriptionWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can use the affected API capability?

A repository administrator can create a new push mirror through the API when mirroring is enabled, even if the site administrator has disabled new push mirrors through the DISABLE_NEW_PUSH setting.

2

What can be sent to a remote created this way?

A push mirror sends all repository refs to a remote selected by the caller. It pushes on each commit or according to its configured schedule.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203