{"api_version":"1","generated_at":"2026-10-06T21:46:39+00:00","cve":"CVE-2026-104632","urls":{"html":"https://cve.report/CVE-2026-104632","api":"https://cve.report/api/cve/CVE-2026-104632.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-104632","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-104632"},"summary":{"title":"Gitea fork workflow approval bypass through cancel and rerun","description":"Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval.","state":"PUBLISHED","assigner":"Gitea","published_at":"2026-10-06 20:17:15","updated_at":"2026-10-06 20:17:15"},"problem_types":[],"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-pvjf-7jrm-6w9g","name":"https://github.com/go-gitea/gitea/security/advisories/GHSA-pvjf-7jrm-6w9g","refsource":"88ee5874-cf24-4952-aea0-31affedb7ff2","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-104632","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-104632","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/DshtAnger","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/DshtAnger"},{"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 blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval."}],"providerMetadata":{"dateUpdated":"2026-10-06T19:22:04.308Z","orgId":"88ee5874-cf24-4952-aea0-31affedb7ff2","shortName":"Gitea"},"references":[{"name":"GitHub Security Advisory GHSA-pvjf-7jrm-6w9g","tags":["vendor-advisory"],"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-pvjf-7jrm-6w9g"},{"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 cancel and rerun"}},"cveMetadata":{"assignerOrgId":"88ee5874-cf24-4952-aea0-31affedb7ff2","assignerShortName":"Gitea","cveId":"CVE-2026-104632","datePublished":"2026-10-06T19:22:04.308Z","dateReserved":"2026-10-04T21:57:35.543Z","dateUpdated":"2026-10-06T19:22:04.308Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-06 20:17:15","lastModifiedDate":"2026-10-06 20:17:15","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"104632","Ordinal":"1","Title":"Gitea fork workflow approval bypass through cancel and rerun","CVE":"CVE-2026-104632","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"104632","Ordinal":"1","NoteData":"Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access cancelled a run that was awaiting approval and then re-ran it, the new jobs were created as waiting rather than blocked while the run still recorded that approval was required. Cancelling and re-running stale fork checks is a routine action that does not involve the approval control, so where Actions is enabled and a matching runner is registered, workflow code taken from the fork pull request head could run on the repository's runners without an explicit approval.","Type":"Description","Title":"Gitea fork workflow approval bypass through cancel and rerun"}]}}}