Gitea · Gitea · published 2026-11-01
CVE-2026-116474Gitea Actions job token spoofing of instance-signed commits
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-116474 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 5% of all CVEs. This Gitea vulnerability: CVSS 6.5 (v3.1). Fixed upstream in Gitea 28.3.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.3.0.
Patch events
DevOpsGitea
Gitea security release: 28.3.0
Upgrade to
28.3.0Why: Vendor security release for server software (most severe: CVE-2026-120263).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (6th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
1.19.0to before28.3.0(affected)
Description (from the CVE record)#
The `GITEA_TOKEN` of a Gitea Actions job authenticates as the `gitea-actions` system user, and the `/api/v1/user` email and GPG key endpoints accepted that user, so a job could register an email address and a GPG key on it; without required email confirmation (the default) the address is stored as activated. Commit verification treats a key without a real owner as the instance signing key, so any user who can run a workflow job could make commits signed with their own key show as trusted and signed by the instance in every repository where they appear, including pull requests to repositories the user cannot write to. The impact is limited to the displayed signature status: enforcement such as required signed commits only checks that a signature is verified and is unaffected, and no access is gained. The `/api/v1/user` routes now reject system users.
Quoted from the CVE Program record.