Gitea
Gitea public-only token bypass through Actions runner registration
Gitea did not reject personal access tokens restricted to public resources (`public-only`) on the organization Actions runner registration-token endpoint, and the runner registered with the resulting token was not limited to public repositories. Holding only such a token with `write:organization` that belongs to an owner of a public organization, an attacker could register an organization-level runner and receive jobs of the organization's private repositories that have Actions enabled, including the workflow content, Actions secrets and variables, and a task token with access to the private repository. The issue widens what the restricted token can reach; it gives nothing beyond what the owner's full account can already do.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 28.3.0
Fixed in 28.3.0
Mitigation
Upgrade Gitea to 28.3.0 or later.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Patch github.com/go-gitea/gitea/pull/39690
- Patch github.com/go-gitea/gitea/pull/39853
2 more
- Release notes blog.gitea.com/release-of-28.3.0
- Release notes github.com/go-gitea/gitea/releases/tag/v28.3.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| afsharid/gitea-cve-2026-116289-detection | 18 Nov 2026 +17 d | 18 Nov 2026 | 0 | Informational · detection |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.