جزئیات آسیب‌پذیری

When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner.

• https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h vendor-advisory
• https://github.com/go-gitea/gitea/pull/37306 patch
• https://blog.gitea.com/release-of-28.0.0/ release-notes
• https://github.com/go-gitea/gitea/releases/tag/v28.0.0 release-notes