{"api_version":"1","generated_at":"2026-10-06T21:45:56+00:00","cve":"CVE-2026-94205","urls":{"html":"https://cve.report/CVE-2026-94205","api":"https://cve.report/api/cve/CVE-2026-94205.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-94205","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-94205"},"summary":{"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.","state":"PUBLISHED","assigner":"Gitea","published_at":"2026-10-06 20:17:34","updated_at":"2026-10-06 20:17:34"},"problem_types":["CWE-441","CWE-863","CWE-441 CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')","CWE-863 CWE-863: Incorrect Authorization"],"metrics":[],"references":[{"url":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0","name":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://blog.gitea.com/release-of-28.0.0/","name":"https://blog.gitea.com/release-of-28.0.0/","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/go-gitea/gitea/pull/39399","name":"https://github.com/go-gitea/gitea/pull/39399","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp","name":"https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-94205","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-94205","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Gitea","product":"Gitea","version":"affected 1.27.3 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"https://github.com/Michael-JRead","lang":"en"},{"source":"CNA","value":"https://github.com/bircni","lang":"en"},{"source":"CNA","value":"https://github.com/silverwind","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","packageName":"gitea.dev","product":"Gitea","vendor":"Gitea","versions":[{"lessThanOrEqual":"1.27.3","status":"affected","version":"0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"reporter","value":"https://github.com/Michael-JRead"},{"lang":"en","type":"remediation developer","value":"https://github.com/bircni"},{"lang":"en","type":"remediation developer","value":"https://github.com/silverwind"}],"descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-441","description":"CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')","lang":"en","type":"CWE"},{"cweId":"CWE-863","description":"CWE-863: Incorrect Authorization","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-06T19:25:04.327Z","orgId":"88ee5874-cf24-4952-aea0-31affedb7ff2","shortName":"Gitea"},"references":[{"name":"GitHub Security Advisory GHSA-xh39-mxw9-34pp","tags":["vendor-advisory"],"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp"},{"name":"Fix: go-gitea/gitea pull request #39399","tags":["patch"],"url":"https://github.com/go-gitea/gitea/pull/39399"},{"name":"Gitea 28.0.0 release announcement","tags":["release-notes"],"url":"https://blog.gitea.com/release-of-28.0.0/"},{"name":"go-gitea/gitea v28.0.0 release","tags":["release-notes"],"url":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0"}],"title":"Gitea fork workflow approval bypass through maintainer-triggered events"}},"cveMetadata":{"assignerOrgId":"88ee5874-cf24-4952-aea0-31affedb7ff2","assignerShortName":"Gitea","cveId":"CVE-2026-94205","datePublished":"2026-10-06T19:25:04.327Z","dateReserved":"2026-10-04T21:57:35.579Z","dateUpdated":"2026-10-06T19:25:04.327Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-06 20:17:34","lastModifiedDate":"2026-10-06 20:17:34","problem_types":["CWE-441","CWE-863","CWE-441 CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')","CWE-863 CWE-863: Incorrect Authorization"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"94205","Ordinal":"1","Title":"Gitea fork workflow approval bypass through maintainer-triggered","CVE":"CVE-2026-94205","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"94205","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"Gitea fork workflow approval bypass through maintainer-triggered"}]}}}