{"id":"CVE-2026-103670","aliases":["BIT-gitea-2026-103670","EUVD-2026-93911","GHSA-4j4g-m7mr-hp5j"],"status":"published","title":"Gitea trusted workflow cancellation by unapproved fork runs","description":"When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-12","score":0.00215,"percentile":0.12075,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-667"],"published":"2026-10-06T19:23:40Z","modified":"2026-10-28T02:30:23Z","fixes":[{"ecosystem":"Bitnami","package":"gitea","fixed_in":["28.0.0"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"gitea","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"28.0.0"}]}]}],"products":[{"vendor":"gitea","product":"gitea"}],"references":[{"url":"https://github.com/go-gitea/gitea/security/advisories/GHSA-4j4g-m7mr-hp5j","tags":["vendor-advisory","Vendor Advisory","advisory"]},{"url":"https://github.com/go-gitea/gitea/pull/39399","tags":["patch","Patch","fix"]},{"url":"https://blog.gitea.com/release-of-28.0.0/","tags":["release-notes","Release Notes","article","advisory"]},{"url":"https://github.com/go-gitea/gitea/releases/tag/v28.0.0","tags":["release-notes","Release Notes","article","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-103670","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/103xxx/CVE-2026-103670.json","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-103670","title":"Gitea trusted workflow cancellation by unapproved fork runs","description":"When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.","status":"published","published":"2026-10-06T19:23:40.05Z","modified":"2026-10-07T15:58:09.298Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"adp"}],"cwes":["CWE-667"],"updated_at":"2026-11-02T13:34:37.420074Z"}],"euvd":[{"id":"EUVD-2026-93911","description":"When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.","status":"published","published":"2026-10-06T19:23:40Z","modified":"2026-10-07T15:58:09Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T17:27:35.164729Z"}],"nvd":[{"id":"CVE-2026-103670","description":"When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.","status":"published","published":"2026-10-06T20:17:14.717Z","modified":"2026-10-15T02:23:07.507Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-667"],"updated_at":"2026-11-02T14:12:54.809359Z"}],"osv":[{"id":"CVE-2026-103670","title":"Gitea trusted workflow cancellation by unapproved fork runs","description":"When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.","status":"published","published":"2026-10-06T19:23:40.05Z","modified":"2026-10-28T02:30:23.09064201Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:44:54.236592Z"},{"id":"BIT-gitea-2026-103670","title":"Gitea trusted workflow cancellation by unapproved fork runs","description":"When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled without checking whether the new run still needed approval. Because fork pull request runs are inserted under the base repository, a user who can open a pull request from a fork could cancel trusted in-progress runs that share a concurrency group with `cancel-in-progress` enabled, without approval and without running any code. On self-hosted runners this can interrupt deployments and leave partial state behind.","status":"published","published":"2026-10-16T08:36:31.082Z","modified":"2026-10-16T09:55:37.323286125Z","updated_at":"2026-11-02T15:28:29.999658Z"}]}}