Gitea fork workflow approval bypass through maintainer-triggered events
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.
- Products
- gitea
- Affected versions
- Not specified
- Fixed versions
- 28.0.0
- CVEs
- CVE-2026-94205
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 12:11 UTC · Revision 1
Source evidence
Gitea fork workflow approval bypass through maintainer-triggered events
core-osv · Original sourcePublished 14 Oct 2026, 08:43 UTC
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.
osv:BIT-gitea-2026-94205
gitea
Fixed versions: 28.0.0
Complete source record
{
"id": "dcb55db43924e54fd2fbc77e33a6421dfc71502e15ba3b569aa6f8b93d5f6235",
"url": "https://osv.dev/vulnerability/BIT-gitea-2026-94205",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Gitea fork workflow approval bypass through maintainer-triggered events",
"summary": "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.",
"evidence": "osv:BIT-gitea-2026-94205",
"products": [
{
"name": {
"value": "gitea",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "28.0.0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "critical",
"structured": {
"id": "BIT-gitea-2026-94205",
"aliases": [
"BIT-gitea-2026-94205",
"CVE-2026-94205",
"GHSA-xh39-mxw9-34pp"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "28.0.0"
}
]
}
],
"package": {
"name": "gitea",
"purl": "pkg:bitnami/gitea",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/gitea/BIT-gitea-2026-94205.json"
}
}
],
"modified": "2026-10-14T11:11:12.983035878Z",
"provider": "osv",
"references": [
"https://blog.gitea.com/release-of-28.0.0/",
"https://github.com/go-gitea/gitea/pull/39399",
"https://github.com/go-gitea/gitea/releases/tag/v28.0.0",
"https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp",
"https://nvd.nist.gov/vuln/detail/CVE-2026-94205"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*"
],
"severity": "Critical"
}
},
"related_cves": [
{
"value": "CVE-2026-94205",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 316257,
"published_at": "2026-10-14T08:43:07.222+00:00"
}