CVE-2026-79960
Gitea deploy key pushes acting as the repository owner
- State
- Published
- Severity
- 7.1 High
- Published
- Oct 6, 2026
- Updated
- Oct 7, 2026
- Reserved
- Oct 4, 2026
Description
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 7.1 High | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N | CISA-ADP |
Weaknesses
- CWE-863 Incorrect Authorization
Affected Products
| Product | Versions |
|---|---|
GiteaGitea |
|
References
- GitHub Security Advisory GHSA-7769-9pr9-m24hvendor-advisory
- Fix: go-gitea/gitea pull request #37306patch
- Gitea 28.0.0 release announcementrelease-notes
- go-gitea/gitea v28.0.0 releaserelease-notes
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.