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.
References
- https://blog.gitea.com/release-of-28.3.0/
- https://github.com/go-gitea/gitea/pull/39690
- https://github.com/go-gitea/gitea/pull/39853
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0
- https://github.com/go-gitea/gitea/security/advisories/GHSA-x5v4-836g-f95x
Collected automatically from public sources. Verify affected versions and fixes in the vendor's notice before acting.