High severity · published Oct 6, 2026
CVE-2026-79960
Gitea deploy key pushes acting as the repository owner
7.1
CVSS
0.2%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 11% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
Gitea · Gitea
through 1.27.3 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-79960
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-79960
vendor-advisory
https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h
patch
https://github.com/go-gitea/gitea/pull/37306
release-notes
https://blog.gitea.com/release-of-28.0.0/
release-notes
https://github.com/go-gitea/gitea/releases/tag/v28.0.0
More from Gitea
9.8
CVE-2026-60004
Gitea Code Injection Vulnerability
9.8
CVE-2026-59774
Gitea Org-mode file disclosure and code execution
9.8
CVE-2026-73278
Gitea WebAuthn bypass during OAuth and OIDC sign-in
9.8
CVE-2026-94205
Gitea fork workflow approval bypass through maintainer-triggered events
9.8
CVE-2022-42968
Gitea before 1.17.3 does not sanitize and escape refs in the git backend
