CVE-2026-129337

Gitea push without write access to repositories still being created

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.

Analysis

AI-generated

Technical impact

The vulnerability allows an attacker with only read permission on a Gitea repository that is still in the creation phase—such as during a migration, fork, or template operation—to push branches or tags because Git over HTTP lowered the required permission for pushes from write to read. Since repositories under creation lack server‑side hooks, the usual enforcement of write access is bypassed. This enables insertion of arbitrary code or data into the repository, compromising integrity and potentially delivering malicious content to downstream consumers.

Affected Systems

Gitea installations running a version prior to 28.4.0 are affected, as that is the release that introduced checks to block pushes to repositories that are still being created.

Risk and Exploitability

The flaw is exploitable via the standard HTTP Git protocol and requires only read‑level access that a legitimate user might be granted. Because the attack requires no additional privileges and affects any repository in a transient state, the risk is moderate to high for environments where users can initiate migrations or forks. The EPSS score is not available, and the vulnerability is not yet listed in CISA’s KEV catalog, but the straightforward nature of the attack vector warrants timely remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.4.0 or later, which enforces write restrictions on repositories that are still being created.
  • Ensure that read permissions to new repositories are granted only after the creation process and any associated hooks have been fully established.
  • During migrations, forks, or template creations, restrict push access or temporarily revoke read permissions from external users until the operation completes.

Generated by OpenCVE AI on November 15, 2026 at 22:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description Git over HTTP lowers the required permission for pushes to read access, so that the AGit flow works, and relies on the repository's server-side hooks to enforce write access. A repository that is still being created by a migration, fork or template generation has no hooks yet, so a user with read access to it could push branches and tags during that window, or after a failed migration that left the repository in that state. Git over HTTP now refuses requests to repositories that are still being created.
Title Gitea push without write access to repositories still being created
Weaknesses CWE-862
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:14 PM
Reserved
Nov 15, 2026, 8:31 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM