CVE-2026-79960

Gitea deploy key pushes acting as the repository owner

Published Oct 6, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

When a Git push is authenticated with a deploy key, Gitea incorrectly records the pusher as the repository owner instead of the deploy key. Because the push hook pipeline then evaluates the owner for permission checks, a user holding a writable deploy key can bypass normal authorization controls. This allows the creation of protected tags even if the tag is not on the allow list and enables modification of repository visibility settings—such as turning a private repository public through push options. Additionally, pull requests created through the AGit flow with a deploy key are incorrectly attributed to the repository owner, potentially obscuring the true contributor.

Affected Systems

All installations of Gitea running versions prior to the release that fixed the issue are affected, specifically Gitea versions before 28.0.0. The vulnerability is present in the core Gitea application regardless of deployment environment or operating system.

Risk and Exploitability

The exploit requires only a deploy key that has write permissions and does not involve complex attacker steps. Although the EPSS score indicates a low probability (<1%) and the vulnerability is not listed in the CISA KEV catalog, the ability to create protected tags and alter repository visibility, coupled with a CVSS score of 7.1, represents a significant privilege escalation risk for exposed or sensitive repositories. The likely attack vector is via deployment of a malicious or misconfigured deploy key, and the risk is heightened for organizations that use deploy keys to automate CI/CD pipelines.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.0.0 or later to apply the vendor patch that corrects the ownership attribution for deploy key pushes.
  • If an upgrade is delayed, revoke any deploy keys that have write permissions until the fix is applied, and re‑generate keys with read‑only or repository‑restricted scopes as a temporary measure.
  • Configure repository settings to enforce tag creation and visibility change permissions through explicit ACLs and enable tag allow lists; consider disabling the use of push options for sensitive settings until the issue is resolved.

Generated by OpenCVE AI on October 7, 2026 at 16:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
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
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 2:21 PM
Reserved
Oct 4, 2026, 9:59 PM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 13, 2026, 4:51 PM