Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.
Metrics
Affected Vendors & Products
References
History
Sat, 17 Oct 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-829 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 13 Oct 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* |
Wed, 07 Oct 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 07 Oct 2026 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Tue, 06 Oct 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval. | |
| Title | Gitea fork workflow approval bypass through maintainer-triggered events | |
| Weaknesses | CWE-441 CWE-863 |
|
| References |
|
Status: PUBLISHED
Assigner: Gitea
Published: 2026-10-06T19:25:04.327Z
Updated: 2026-10-07T20:11:55.392Z
Reserved: 2026-10-04T21:57:35.579Z
Link: CVE-2026-94205
Updated: 2026-10-07T20:11:50.295Z
Status : Analyzed
Published: 2026-10-06T20:17:34.733
Modified: 2026-10-13T16:41:45.587
Link: CVE-2026-94205