CVE-2026-119441
Gitea public-only token bypass on bulk organization repository deletion
CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th
`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.
| CWE | CWE-863 |
| Vendor | gitea |
| Product | gitea |
| Published | Nov 1, 2026 |
Stay Ahead of the Next One
Get instant alerts for gitea gitea
Be the first to know when new unknown vulnerabilities affecting gitea gitea are published โ delivered to Slack, Telegram or Discord.
Get Free Alerts โ
Free ยท No credit card ยท 60 sec setup
Affected Versions
Gitea / Gitea
1.27.0 < 28.3.0
References
github.com: https://github.com/go-gitea/gitea/security/advisories/GHSA-jh8p-x4ch-389q github.com: https://github.com/go-gitea/gitea/pull/39690 github.com: https://github.com/go-gitea/gitea/pull/39853 blog.gitea.com: https://blog.gitea.com/release-of-28.3.0/ github.com: https://github.com/go-gitea/gitea/releases/tag/v28.3.0
Credits
๐ https://github.com/K3y5tr0ke https://github.com/silverwind