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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/37306 Patch
- https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.1 · giteaNVD modified 2026-10-13 16:51
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*