Live › vulnerability › CVE-2026-116289
Gitea accepted personal access tokens restricted to public resources when registering organization-level Actions runners. A runner registered with such a token can receive jobs from the organization's private repositories, exposing workflow content, Actions secrets and variables, and a task token for the private repository.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-01 10:49 UTC. All times on this page are UTC.
Teams that self-host Gitea with organization-level Actions runners and private repositories that use Actions. The attacker needs a token owned by an owner of a public organization with write:organization scope, and the exposure is limited to what that owner's full account can already reach. Instances without Actions enabled or without organization-level runners are not affected.
No product ranges from the sources yet.
gitea --version. Affected and fixed versions are not yet published by Gitea (unknown); watch https://github.com/go-gitea/gitea/security/advisories and the release changelog, and move to the newest 1.27.x patch release.public-only scope with write:organization; revoke ones you do not need.Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-116289")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.