CVE-2026-125423
Gitea command execution through repository auto-initialization
Description
A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.
INFO
Published Date :
Nov. 15, 2026, 9:16 p.m.
Last Modified :
Nov. 15, 2026, 9:16 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Ensure repository initialization completes before accepting pushes.
- Validate git hook integrity after initialization.
- Restrict push access during critical initialization phases.
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-125423.
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-125423 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-125423
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-125423 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-125423 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 A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete. Added CWE CWE-362 Added CWE CWE-59 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/125xxx/CVE-2026-125423.json">CVE-2026-125423</a> Added Reference https://blog.gitea.com/release-of-28.4.0/ Added Reference https://github.com/go-gitea/gitea/pull/40376 Added Reference https://github.com/go-gitea/gitea/pull/40383 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.4.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946