{"api_version":"1","generated_at":"2026-10-06T21:46:27+00:00","cve":"CVE-2026-79960","urls":{"html":"https://cve.report/CVE-2026-79960","api":"https://cve.report/api/cve/CVE-2026-79960.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-79960","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-79960"},"summary":{"title":"Gitea deploy key pushes acting as the repository owner","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.","state":"PUBLISHED","assigner":"Gitea","published_at":"2026-10-06 20:17:33","updated_at":"2026-10-06 20:17:33"},"problem_types":["CWE-863","CWE-863 CWE-863: Incorrect Authorization"],"metrics":[],"references":[{"url":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0","name":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h","name":"https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://blog.gitea.com/release-of-28.0.0/","name":"https://blog.gitea.com/release-of-28.0.0/","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/go-gitea/gitea/pull/37306","name":"https://github.com/go-gitea/gitea/pull/37306","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-79960","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-79960","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Gitea","product":"Gitea","version":"affected 1.27.3 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"https://github.com/1K0CT","lang":"en"},{"source":"CNA","value":"https://github.com/ToastyTheBot","lang":"en"},{"source":"CNA","value":"https://github.com/silverwind","lang":"en"},{"source":"CNA","value":"https://github.com/bircni","lang":"en"},{"source":"CNA","value":"https://github.com/wxiaoguang","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","packageName":"gitea.dev","product":"Gitea","vendor":"Gitea","versions":[{"lessThanOrEqual":"1.27.3","status":"affected","version":"0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"reporter","value":"https://github.com/1K0CT"},{"lang":"en","type":"remediation developer","value":"https://github.com/ToastyTheBot"},{"lang":"en","type":"remediation developer","value":"https://github.com/silverwind"},{"lang":"en","type":"remediation developer","value":"https://github.com/bircni"},{"lang":"en","type":"remediation developer","value":"https://github.com/wxiaoguang"}],"descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-863","description":"CWE-863: Incorrect Authorization","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-06T19:24:55.742Z","orgId":"88ee5874-cf24-4952-aea0-31affedb7ff2","shortName":"Gitea"},"references":[{"name":"GitHub Security Advisory GHSA-7769-9pr9-m24h","tags":["vendor-advisory"],"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24h"},{"name":"Fix: go-gitea/gitea pull request #37306","tags":["patch"],"url":"https://github.com/go-gitea/gitea/pull/37306"},{"name":"Gitea 28.0.0 release announcement","tags":["release-notes"],"url":"https://blog.gitea.com/release-of-28.0.0/"},{"name":"go-gitea/gitea v28.0.0 release","tags":["release-notes"],"url":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0"}],"title":"Gitea deploy key pushes acting as the repository owner"}},"cveMetadata":{"assignerOrgId":"88ee5874-cf24-4952-aea0-31affedb7ff2","assignerShortName":"Gitea","cveId":"CVE-2026-79960","datePublished":"2026-10-06T19:24:55.742Z","dateReserved":"2026-10-04T21:59:53.563Z","dateUpdated":"2026-10-06T19:24:55.742Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-06 20:17:33","lastModifiedDate":"2026-10-06 20:17:33","problem_types":["CWE-863","CWE-863 CWE-863: Incorrect Authorization"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"79960","Ordinal":"1","Title":"Gitea deploy key pushes acting as the repository owner","CVE":"CVE-2026-79960","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"79960","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Gitea deploy key pushes acting as the repository owner"}]}}}