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.
References
Configurations
No configuration.
History
14 Oct 2026, 16:17
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 6.5 |
14 Oct 2026, 15:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-14 15:17
Updated : 2026-10-14 16:17
NVD link : CVE-2026-66874
Mitre link : CVE-2026-66874
CVE.ORG link : CVE-2026-66874
JSON object : View
Products Affected
No product.
