{"id":"CVE-2026-94205","aliases":["BIT-gitea-2026-94205","EUVD-2026-93919","GHSA-xh39-mxw9-34pp"],"status":"published","title":"Gitea fork workflow approval bypass through maintainer-triggered events","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.","severity":{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-10","score":0.00622,"percentile":0.50158,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-441","CWE-863"],"published":"2026-10-06T19:25:04Z","modified":"2026-10-28T02:30:32Z","fixes":[{"ecosystem":"Bitnami","package":"gitea","fixed_in":["28.0.0"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"gitea","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"28.0.0"}]}]}],"products":[{"vendor":"gitea","product":"gitea"}],"references":[{"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp","tags":["vendor-advisory","Exploit","Mitigation","Vendor Advisory","advisory"]},{"url":"https://github.com/go-gitea/gitea/pull/39399","tags":["patch","Patch","fix"]},{"url":"https://blog.gitea.com/release-of-28.0.0/","tags":["release-notes","Release Notes","article","advisory"]},{"url":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0","tags":["release-notes","Release Notes","article","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94205","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/94xxx/CVE-2026-94205.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-94205","title":"Gitea fork workflow approval bypass through maintainer-triggered events","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.","status":"published","published":"2026-10-06T19:25:04.327Z","modified":"2026-10-07T20:11:55.392Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"adp"}],"cwes":["CWE-441","CWE-863"],"updated_at":"2026-11-02T14:19:53.786088Z"}],"euvd":[{"id":"EUVD-2026-93919","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.","status":"published","published":"2026-10-06T19:25:04Z","modified":"2026-10-07T20:11:55Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T17:27:33.904651Z"}],"nvd":[{"id":"CVE-2026-94205","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.","status":"published","published":"2026-10-06T20:17:34.733Z","modified":"2026-10-13T16:41:45.587Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"secondary"}],"cwes":["CWE-441","CWE-863"],"updated_at":"2026-11-02T14:12:54.809359Z"}],"osv":[{"id":"CVE-2026-94205","title":"Gitea fork workflow approval bypass through maintainer-triggered events","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.","status":"published","published":"2026-10-06T19:25:04.327Z","modified":"2026-10-28T02:30:32.65800998Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-441","CWE-863"],"updated_at":"2026-11-02T15:45:20.931171Z"},{"id":"BIT-gitea-2026-94205","title":"Gitea fork workflow approval bypass through maintainer-triggered events","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.","status":"published","published":"2026-10-14T08:43:07.222Z","modified":"2026-10-14T11:11:12.983035878Z","updated_at":"2026-11-02T15:28:29.999658Z"}]}}