CVE-2026-129337
Gitea push without write access to repositories still being created
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.
INFO
Published Date :
Nov. 15, 2026, 10:17 p.m.
Last Modified :
Nov. 15, 2026, 10:17 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Refuse HTTP requests to repositories being created.
- Ensure server-side hooks enforce write access.
- Verify repository migration completion.
- Check for failed migrations.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-129337.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-129337 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-129337
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-129337 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-129337 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 88ee5874-cf24-4952-aea0-31affedb7ff2
Nov. 15, 2026
Action Type Old Value New Value 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. Added CWE CWE-862 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/129xxx/CVE-2026-129337.json">CVE-2026-129337</a> Added Reference https://blog.gitea.com/release-of-28.4.0/ Added Reference https://github.com/go-gitea/gitea/pull/40120 Added Reference https://github.com/go-gitea/gitea/pull/40268 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.4.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-8cjj-9p56-j54f