CVE-2026-118395 PUBLISHED

Gitea public-only token bypass in repository and organization creation

Assigner: Gitea
Reserved: 01.11.2026 Published: 01.11.2026 Updated: 01.11.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.

Product Status

Vendor Gitea
Product Gitea
Versions Default: unaffected
  • affected from 0 to 28.3.0 (excl.)

Credits

  • https://github.com/DshtAnger reporter
  • https://github.com/tao0845 reporter
  • https://github.com/d3do-23 reporter
  • https://github.com/venkatchalla06 reporter
  • https://github.com/shmulc8 reporter
  • https://github.com/silverwind remediation developer

References