CVE-2026-89182
Gitea push-to-create bypass of FORCE_PRIVATE policy
Description
With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.
INFO
Published Date :
Oct. 6, 2026, 10:17 p.m.
Last Modified :
Oct. 6, 2026, 10:17 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Update the post-receive hook script.
- Ensure the hook enforces the FORCE_PRIVATE configuration.
- Test repository creation and visibility settings.
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-89182.
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-89182 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-89182
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-89182 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-89182 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
Oct. 06, 2026
Action Type Old Value New Value Added Description With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected. Added CWE CWE-863 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/89xxx/CVE-2026-89182.json">CVE-2026-89182</a> Added Reference https://blog.gitea.com/release-of-28.1.0/ Added Reference https://github.com/go-gitea/gitea/pull/39501 Added Reference https://github.com/go-gitea/gitea/pull/39507 Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.1.0 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgc