Gitea deploy key pushes acting as the repository owner
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.
- Products
- gitea
- Affected versions
- Not specified
- Fixed versions
- 28.0.0
- CVEs
- CVE-2026-79960
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 12:06 UTC · Revision 1
Source evidence
Gitea deploy key pushes acting as the repository owner
core-osv · Original sourcePublished 14 Oct 2026, 08:43 UTC
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.
osv:BIT-gitea-2026-79960
gitea
Fixed versions: 28.0.0
Complete source record
{
"id": "ef3e875026453d4b045a23417e80121c7811f7fa557036fa79d97c4e79b1da29",
"url": "https://osv.dev/vulnerability/BIT-gitea-2026-79960",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Gitea deploy key pushes acting as the repository owner",
"summary": "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.",
"evidence": "osv:BIT-gitea-2026-79960",
"products": [
{
"name": {
"value": "gitea",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "28.0.0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "BIT-gitea-2026-79960",
"aliases": [
"BIT-gitea-2026-79960",
"CVE-2026-79960",
"GHSA-7769-9pr9-m24h"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "28.0.0"
}
]
}
],
"package": {
"name": "gitea",
"purl": "pkg:bitnami/gitea",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/gitea/BIT-gitea-2026-79960.json"
}
}
],
"modified": "2026-10-14T11:11:00.096062575Z",
"provider": "osv",
"references": [
"https://blog.gitea.com/release-of-28.0.0/",
"https://github.com/go-gitea/gitea/pull/37306",
"https://github.com/go-gitea/gitea/releases/tag/v28.0.0",
"https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h",
"https://nvd.nist.gov/vuln/detail/CVE-2026-79960"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*"
],
"severity": "High"
}
},
"related_cves": [
{
"value": "CVE-2026-79960",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 316243,
"published_at": "2026-10-14T08:43:02.338+00:00"
}