llamaCVEVulnerability Intelligence
/
Gitea

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.

Specific setups onlySin parche publicadosignature verification bypass
Descargar PNG JSON
CVSS 3.1
6.5
Media
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Fuente: CISA-ADP
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición18 dDesde la divulgación, 1 nov 2026, 4:48 a. m.
Detección5 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, no automatizable e impacto técnico parcial. No hay versión corregida: aplique mitigaciones.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +1
Fuente: OSV
Verificada
1 nov 26
6 nov 26
18 nov 26
19 nov 26
1 nov 26
5 nov 26
10 nov 26
15 nov 26
19 nov 26
FechaFaseEventoDetalle
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
Resumen
Resumen generado por IA · CC-BY 4.0

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.

¿Qué significa?A regular user who can run one Gitea Actions job can make commits signed with their own GPG key display as signed by the instance itself and trusted, in every repository where the commit appears. Only the displayed signature status is affected, and no access is gained.
¿Quién está afectado?Gitea versions 1.19.0 through 28.2.0 with Gitea Actions enabled (the default) and REGISTER_EMAIL_CONFIRM set to false (also the default). Instances that require email confirmation with a working mailer are not affected. The version can be checked with gitea --version, and the setting in the app.ini configuration file.
¿Qué hacer?Upgrade to Gitea 28.3.0 or later, the fixed version listed for this vulnerability.
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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Gitea Actions enabled (default)“The attack works on default settings (Actions enabled, REGISTER_EMAIL_CONFIRM = false )”
02
Email confirmation not required (REGISTER_EMAIL_CONFIRM = false, the default); instances requiring confirmation with a working mailer are not affected“Instances that require e-mail confirmation with a working mailer are not affected.”
03
Gitea versions 1.19.0 through 28.2.0“>= 1.19.0, <= 28.2.0”
¿Quién debe revisar?Gitea instances from 1.19.0 through 28.2.0 with Actions enabled and no email confirmation, and teams that review pull requests or depend on the instance signature badge
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CISA-ADP
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:N
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
gitea.dev≥ 1.19.0 ≤ 28.2.0
gitea.dev≥ 1.19.0 < 28.3.0
1.19.0
v1.27.3
28.2.0
28.3.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogitea.dev
Sin parche — — v1.27.3 afectada
Versiones corregidas28.3.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/go-gitea/gitea/security/advisories/GHSA-mf6p-vqpw-3r7x
Fabricantehttps://blog.gitea.com/release-of-28.3.0/
Parchehttps://github.com/go-gitea/gitea/pull/39945
Parchehttps://github.com/go-gitea/gitea/pull/40115
Otrahttps://github.com/go-gitea/gitea/releases/tag/v28.3.0

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.