Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather…
Gitea · Gitea
Gitea Actions, in the Gitea product, incorrectly decides whether a run triggered by a fork pull request needs approval, basing the decision on the maintainer who triggered the event (such as adding a label during triage) rather than the pull request author, while the workflow definition is still taken from the fork head. An attacker who can open a fork pull request can have fork-controlled workflow code run on the base repository's registered runners without an explicit approval, provided Actions is enabled and a matching runner exists and no maintainer approval gate intervenes.
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.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 6 Oct 2026. No public exploit code or confirmed exploitation is recorded.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
What security researchers reported
Not named in any threat report yetAlso mentioned in 8 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Known_Cve | Oct 15, 2026 | Part 1/314 Oct 2026
- Known_Cve | Oct 14, 2026 | Part 1/313 Oct 2026
- Known_Cve | Oct 13, 2026 | Part 1/212 Oct 2026
- Known_Cve | Oct 12, 2026 | Part 1/211 Oct 2026
- Known_Cve | Oct 11, 2026 | Part 1/210 Oct 2026
- Known_Cve | Oct 10, 2026 | Part 2/29 Oct 2026
- 2 more on OTX