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.
Metrics
Affected Vendors & Products
References
History
Tue, 13 Oct 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* |
Wed, 07 Oct 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 07 Oct 2026 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Tue, 06 Oct 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Gitea deploy key pushes acting as the repository owner | |
| Weaknesses | CWE-863 | |
| References |
|
Status: PUBLISHED
Assigner: Gitea
Published: 2026-10-06T19:24:55.742Z
Updated: 2026-10-07T14:21:39.950Z
Reserved: 2026-10-04T21:59:53.563Z
Link: CVE-2026-79960
Updated: 2026-10-07T14:20:18.700Z
Status : Analyzed
Published: 2026-10-06T20:17:33.660
Modified: 2026-10-13T16:51:21.447
Link: CVE-2026-79960
No data.