Gitea fork workflow approval bypass through cancel and rerun
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-104632
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 00:08 UTC · Revision 1
Source evidence
Gitea fork workflow approval bypass through cancel and rerun
core-osv · Original sourcePublished 6 Oct 2026, 19:22 UTC
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.
osv:CVE-2026-104632
Complete source record
{
"id": "6f6010aedec3be9bccf555c02f91b3f9d7624179acb635b99c76e3f57ec2bc34",
"url": "https://osv.dev/vulnerability/CVE-2026-104632",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Gitea fork workflow approval bypass through cancel and rerun",
"summary": "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.",
"evidence": "osv:CVE-2026-104632",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-104632",
"aliases": [
"BIT-gitea-2026-104632",
"CVE-2026-104632",
"GHSA-pvjf-7jrm-6w9g"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/go-gitea/gitea",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "15b8a5805adf57c5189602008d38cccfd3c795e0"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "28.0.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "15b8a5805adf57c5189602008d38cccfd3c795e0"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v28.0.0"
}
]
}
}
],
"versions": [
"v29.0.0-dev",
"v1.28.0-dev",
"v1.27.0-dev",
"v1.26.0-dev",
"v1.25.0-dev",
"v1.24.0-dev",
"v1.22.0-rc1",
"v1.23.0-dev",
"v1.22.0-rc0",
"v1.21.0-rc0",
"v1.22.0-dev",
"v1.20.0-rc0",
"v1.21.0-dev",
"v1.20.0-dev",
"v1.19.0-rc0",
"v1.18.0-rc0",
"v1.19.0-dev",
"v1.18.0-dev",
"v1.17.0-dev",
"v1.16.0-rc1",
"v1.15.0-rc1",
"v1.16.0-dev",
"v1.15.0-dev",
"v1.14.0-dev",
"v1.13.0-dev",
"v1.12.0-dev",
"v1.10.5",
"v1.11.0-rc1",
"v1.10.0-rc1",
"v1.11.0-dev",
"v1.9.0-rc1",
"v1.10.0-dev",
"v1.9.0-dev",
"v1.7.0-dev",
"v1.6.0-rc1",
"v1.6.0-dev",
"v1.5.0-rc1",
"v1.5.0-dev",
"v1.1.0",
"v1.0.0",
"v0.9.99"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-104632.json"
}
}
],
"modified": "2026-10-28T02:30:45.127673078Z",
"provider": "osv",
"references": [
"https://blog.gitea.com/release-of-28.0.0/",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104632.json",
"https://github.com/go-gitea/gitea/releases/tag/v28.0.0",
"https://github.com/go-gitea/gitea/security/advisories/GHSA-pvjf-7jrm-6w9g",
"https://nvd.nist.gov/vuln/detail/CVE-2026-104632",
"https://github.com/go-gitea/gitea/pull/39399"
],
"provider_metadata": {
"cna_assigner": "Gitea",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/104xxx/CVE-2026-104632.json"
}
},
"related_cves": [
{
"value": "CVE-2026-104632",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 513344,
"published_at": "2026-10-06T19:22:04.308+00:00"
}