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.
{
"cna_assigner": "Gitea",
"cwe_ids": [
"CWE-284",
"CWE-345",
"CWE-693",
"CWE-807"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/66xxx/CVE-2026-66874.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "1.27.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"original_tag": "v1.27.3",
"range": [
{
"fixed": "146cc3eec57174711eac0e0a0c7b38670c6e3922"
}
],
"source": "REFERENCES_TAG"
}
]
}