Quick answers
- Is CVE-2026-116289 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116289 being exploited in the wild.
- How severe is CVE-2026-116289?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-116289?
- Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116289 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-116289?
- Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Gitea 28.3.0
Technical details
The vulnerability is a token scope bypass in the organization Actions runner registration endpoint. An attacker holding a "public-only" personal access token with write:organization scope, on an account that owns a public organization, could register an organization-level runner without scope validation, receiving jobs from private repositories. The issue affects only organizations where the attacker is an owner; it does not expand beyond what the owner's full account can already access.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed