CVE-2026-118395
Published:November 01, 2026
Updated:November 12, 2026
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.
Affected Packages
https://github.com/go-gitea/gitea.git (GITHUB):
Affected version(s) >=v1.20.0-rc0 <v28.3.0Fix Suggestion:
Update to version v28.3.0Related Resources (8)
Do you need more information?
Contact UsCVSS v4
Base Score:
8.7
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
NONE
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
7.5
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Weakness Type (CWE)
Improper Access Control
EPSS
Base Score:
0.28