Sigma detection rules, lab and findings for CVE-2026-116289 (Gitea public-only PAT to org Actions runner)
Sigma rules for CVE-2026-116289 / GHSA-qcgm-ggp8-22qc, built and tested in a local lab against Gitea 28.2.0 (vulnerable) and 28.3.0 (patched).
| Severity | CVSS 3.1 6.5 Medium (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N), per the official advisory |
| Affected | Gitea ≤ 28.2.0 |
| Fixed | 28.3.0 (commit 01db50f0bf) |
| Weakness | CWE-863 Incorrect Authorization |
A personal access token scoped public-only,write:organization that belongs to an org
owner could request an org-level runner registration token for a public organization.
The runner registered with it did not inherit the public-only restriction, so it could
receive jobs, secrets and a GITEA_TOKEN from the org's private repositories. The fix
rejects public-only tokens in reqOrgOwnership() with HTTP 403.
All rules are in rules/combined.yml (logsource: product: gitea, service: router).
| Rule | Level | What it shows |
|---|---|---|
| Registration token issued via API | low | Hunting/audit. On ≤ 28.2.0 it fires on abuse and on legitimate provisioning. |
Registration token request rejected (403, reqOrgOwnership) | medium | On ≥ 28.3.0: a public-only token or a non-owner tried to mint an org runner token. |
Runner Register RPC | informational | Base rule and runner inventory. |
| Token issued → runner registered on same instance (correlation) | low | Time-only pairing on one instance. |
Lab-verified on 2026-11-18 unless marked otherwise.
POST /api/v1/orgs/{org}/actions/runners/registration-token
with a public-only,write:organization PAT returns 200 with a token on 28.2.0 and
403 this endpoint is not available for public-only tokens on 28.3.0. A normal
write:organization PAT returns 200 on both.@ v1/api.go:500(v1.reqOrgOwnership.1). The public-only check runs inside
reqOrgOwnership, so the log names that middleware for both public-only tokens and
non-owners.tokenRequiresScopes is api.go:329
on 28.2.0 and :335 on 28.3.0). Rules match function names, never file:line.POST /api/actions/runner.v1.RunnerService/Register
appears with status 200 on both versions.192.168.97.1 vs runner container 192.168.97.4). A correlation that
groups by src_ip never fires.?x=1), a trailing slash and a different
org-name case (PublicOrg) all return 200 and are logged with the raw path.read:repository, so the scope check fired first.<= 28.2.0.src_ip.access_token, action_runner,
action_task joined with repository.is_private).cd lab && docker compose -p giteacve up -d # 28.2.0 on :3082, 28.3.0 on :3083
./lab/repro.sh # registration-token step only: 200 vs 403
tests/check.sh # rules vs logs/router-sample.log
uv tool run --python 3.12 --from sigma-cli sigma check rules/combined.yml
repro.sh only requests a registration token. It does not register a runner or take
any job or secret. lab/seed.env holds lab-only credentials and is not committed.
Test results (2026-11-18): sigma check 0 errors / 0 issues; rule hits 7 / 1 / 2;
correlation 5 pairs. Path variants with a query string, a trailing slash and a
different org-name case also match. tests/run_rules.py is a minimal evaluator for the
modifiers these rules use. It is not a SIEM backend; test the rules in your own SIEM.
Not lab-tested: the GET, repo, user and admin registration-token routes; the admin-route branch of the 403 rule; behaviour behind a reverse proxy.
The analysis and rule drafts were produced with Claude Fable 5.2 through the Claude API
(research/), then tested in the lab and corrected. The lab tests found two
issues in the drafts: the src_ip grouping of the correlation and an outdated ATT&CK
tactic tag.
Rules and documentation: Detection Rule License (DRL) 1.1.