CVE-2026-116474
Gitea signature verification bypass in Actions commit signing
A workflow job can register a key on the system account so commits appear signed and verified by the instance.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Fuente: CISA-ADP
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-116474 divulgada · CVSS 6.5 (CISA-ADP) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Gitea, the self-hosted Git service, is affected through its Actions feature, where a workflow job could register a GPG key and email address on the built-in system account and cause commits signed with that key to display as verified and signed by the instance. The impact is limited to misleading signature status shown in repositories and pull requests, since signature enforcement and access controls are not affected.
Affects Gitea 1.19.0 through 28.2.0 with Gitea Actions enabled and email confirmation off, both defaults. Fixed in 28.3.0.
Descripción original del registro (Gitea)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
gogitea.dev |
Sin parche | — | — | v1.27.3 afectada |
28.3.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/go-gitea/gitea/security/advisories/GHSA-mf6p-vqpw-3r7xhttps://blog.gitea.com/release-of-28.3.0/https://github.com/go-gitea/gitea/pull/39945https://github.com/go-gitea/gitea/pull/40115https://github.com/go-gitea/gitea/releases/tag/v28.3.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
