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.
CVSS
No CVSS.
References
Configurations
No configuration.
History
01 Nov 2026, 10:18
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-11-01 10:18
Updated : 2026-11-01 10:18
NVD link : CVE-2026-118395
Mitre link : CVE-2026-118395
CVE.ORG link : CVE-2026-118395
JSON object : View
Products Affected
No product.
CWE
No CWE.
