Auth bypass in Gitea
CVE-2026-116289
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.
Vulnerability class: Broken Access Control
Published · last modified .
EPSS exploit prediction
EPSS: 0.002 (9.6th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 10th percentile — 9.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
The 30-day trend appears once there are two daily scores.
Affected products
Weakness classification (CWE)
References
- 88ee5874-cf24-4952-aea0-31affedb7ff2 (vendor-advisory)
- 88ee5874-cf24-4952-aea0-31affedb7ff2 (patch)
- 88ee5874-cf24-4952-aea0-31affedb7ff2 (patch)
- 88ee5874-cf24-4952-aea0-31affedb7ff2 (release-notes)
- 88ee5874-cf24-4952-aea0-31affedb7ff2 (release-notes)