Gitea public-only token bypass on bulk organization repository deletion
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Gitea 28.3.0.
`DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could therefore permanently delete the organization's private repositories, which such a token must not reach. Routes that require organization ownership now reject public-only tokens.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Gitea | Gitea | >=1.27.0 <28.3.0 | 28.3.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Gitea, strongest first
Embed
A live severity badge for an advisory, README or ticket