0.0
NA
CVE-2026-118395
Gitea public-only token bypass in repository and organization creation
Description

Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and `POST /api/v1/repos/{owner}/{repo}/generate` still accepted such tokens. A holder of a public-only token with the needed write scopes could create private repositories in organizations where the token's owner may create repositories, create private organizations, and generate private repositories from templates. The token still could not read the private repositories it created.

INFO

Published Date :

Nov. 1, 2026, 10:18 a.m.

Last Modified :

Nov. 1, 2026, 10:18 a.m.

Remotely Exploit :

No

Source :

88ee5874-cf24-4952-aea0-31affedb7ff2
Affected Products

The following products are affected by CVE-2026-118395 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Update Gitea to patch authorization issues with public-only tokens.
  • Update Gitea to the latest version.
  • Verify token restrictions are correctly enforced.
  • Test repository creation endpoints.
  • Review related authorization configurations.
References to Advisories, Solutions, and Tools
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-118395 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-118395 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-118395 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-118395 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. 01, 2026

    Action Type Old Value New Value
    Added Description Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and `POST /api/v1/repos/{owner}/{repo}/generate` still accepted such tokens. A holder of a public-only token with the needed write scopes could create private repositories in organizations where the token's owner may create repositories, create private organizations, and generate private repositories from templates. The token still could not read the private repositories it created.
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/118xxx/CVE-2026-118395.json">CVE-2026-118395</a>
    Added Reference https://blog.gitea.com/release-of-28.3.0/
    Added Reference https://github.com/go-gitea/gitea/pull/39690
    Added Reference https://github.com/go-gitea/gitea/pull/39853
    Added Reference https://github.com/go-gitea/gitea/releases/tag/v28.3.0
    Added Reference https://github.com/go-gitea/gitea/security/advisories/GHSA-x5v4-836g-f95x
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.