CVE-2026-66874
Gitea required Actions check bypass through skipped workflows
- State
- Published
- Severity
- 6.5 Medium
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Reserved
- Aug 13, 2026
Description
For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status context but deliberately prevent it from running. Because skipped statuses count as success, branch protection or organization-required workflow checks can appear satisfied without the mandated workflow executing; no runner or maintainer approval is required for this path.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 6.5 Medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N | CISA-ADP |
Weaknesses
Affected Products
| Product | Versions |
|---|---|
GiteaGitea |
|
References
- GitHub Security Advisory GHSA-5xp7-r6cr-39ffvendor-advisory
- Gitea 1.27.3 release announcementrelease-notes
- Fix: go-gitea/gitea pull request #39005patch
- Fix: go-gitea/gitea pull request #39018patch
- go-gitea/gitea v1.27.3 releaserelease-notes
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.