Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.
https://github.com/go-gitea/gitea/security/advisories/GHSA-8cjj-9p56-j54f
https://github.com/go-gitea/gitea/releases/tag/v28.4.0
https://github.com/go-gitea/gitea/pull/40268
https://github.com/go-gitea/gitea/pull/40120