Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sun, 01 Nov 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Sun, 01 Nov 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Gitea Actions fork workflow trust through pull request review commit | |
| Weaknesses | CWE-863 | |
| References |
|
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-11-01T09:47:07.487Z
Reserved: 2026-11-01T08:48:41.145Z
Link: CVE-2026-118386
No data.
Status : Deferred
Published: 2026-11-01T10:18:36.073
Modified: 2026-11-01T10:18:36.187
Link: CVE-2026-118386
No data.
OpenCVE Enrichment
Updated: 2026-11-01T11:45:05Z