CVEsGiteaCVE-2026-119441Published Nov 1, 09:48 · Updated Nov 1, 09:48 UTC
–
Not scored
CVE-2026-119441

Gitea public-only token bypass on bulk organization repository deletion

gitea.dev · Incorrect authorization · CWE-863
Affectedgitea.dev
FixUpdate to 28.3.0 or newer
PublishedNov 1, 09:48 · Gitea
ScoredNot yet
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:08 UTC

What we know

No known exploitation. CISA KEV, checked 22:08 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
No severity score yet.

Description

`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.

From Gitea

Affected and fixed versions

ProductAffectedFixed ingitea.dev1.27.0 – before 28.3.028.3.0

Exploit code

Exploit-DBnone knownMetasploitnone knownNucleinone known

References

GitHub Security Advisory GHSA-jh8p-x4ch-389q · github.comvendor advisoryFix: go-gitea/gitea pull request #39690 · github.compatchFix backport to release/v28: go-gitea/gitea pull request #39853 · github.compatchGitea 28.3.0 release announcement · blog.gitea.comrelease notesgo-gitea/gitea v28.3.0 release · github.comrelease notes

Other CVEs in gitea.dev

All 70 →
–Gitea limited-visibility profile disclosure with public-only tokens · CVE-2026-119627Nov 1–Gitea user and organization feed token scope bypass · CVE-2026-119625Nov 1–Gitea private pull request disclosure on project boards · CVE-2026-119533Nov 1