Live › vulnerability › CVE-2026-118386
Gitea Actions read workflows from a commit named in a pull request review instead of the pull request head, so a user with read access can plant a commit and run it without approval. The attacker's workflow receives the repository's and owner's Actions secrets and a GITEA_TOKEN with write access.
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.
Self-hosted Gitea instances with Actions enabled and a runner serving the repository. A user with read access (for example via a fork pull request or AGit push) can plant a commit, submit a review naming it on a pull request whose head branch is in the same repository, and the workflow runs without approval with the repository's and owner's Actions secrets and a write-capable GITEA_TOKEN. Instances without runners can skip it; fixed in 28.3.0.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| gitea | vendor | < 28.3.0 (oldest affected version not stated by Gitea) | 28.3.0 |
gitea --version; versions before 28.3.0 contain the flaw (Gitea's post names 28.3.0 as the fix; it does not state the oldest affected version, so treat older releases as exposed).28.3.0, which makes pull_request_review workflows run on the pull request headEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Workflows triggered by a pull request review were read from the commit named in the review's commit_id, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker's workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a GITEA_TOKEN with write access to the repository. Review-triggered workflows now run on the pull request head.
This page as .md · .json · in your agent: get_signal("CVE-2026-118386")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.