CVE-2026-70396
Gitea organization repository creation token scope bypass
Description
Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories if the authorizing user has permission to do so. This bypasses the token's delegated scope boundary while remaining subject to the user's organization permissions.
INFO
Published Date :
Oct. 14, 2026, 3:17 p.m.
Last Modified :
Oct. 14, 2026, 4:04 p.m.
Remotely Exploit :
No
Source :
88ee5874-cf24-4952-aea0-31affedb7ff2
Solution
- Update API to require write:repository scope.
- Review all repository creation routes.
- Enforce scope checks consistently.
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-70396.
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-70396 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-70396
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-70396 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-70396 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. 14, 2026
Action Type Old Value New Value Added Description Gitea's organization repository-creation API requires write:organization but omits the write:repository token scope enforced by other repository-creation routes. A personal access token or OAuth application token without repository-write scope can therefore create organization-owned repositories if the authorizing user has permission to do so. This bypasses the token's delegated scope boundary while remaining subject to the user's organization permissions. Added CWE CWE-863 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/70xxx/CVE-2026-70396.json">CVE-2026-70396</a> Added Reference https://blog.gitea.com/release-of-1.27.3/ Added Reference https://github.com/go-gitea/gitea/pull/39007 Added Reference https://github.com/go-gitea/gitea/pull/39014 Added Reference https://github.com/go-gitea/gitea/releases/tag/v1.27.3 Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-hxhc-246f-rvqc