llamaCVEVulnerability Intelligence
/
Gitea

CVE-2026-118386

Gitea authorization bypass in Actions review-triggered workflows

A user with only read access can run a workflow that reaches Actions secrets and a token with repo write access.

Specific setups onlySin parche publicadoauthorization bypass
Descargar PNG JSON
CVSS 3.1
6.5
Media
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:47 a. m.
Detección6 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-118386 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 when its Actions feature runs workflows triggered by pull request reviews. An attacker with only read access to a repository could run their own workflow there, gaining access to that repository's and its owner's Actions secrets and a token with write access to the repository.

Affects Gitea 1.19.0 through versions before 28.3.0 where a runner serves the repository and a pull request has its head branch in the repository itself. Fixed in 28.3.0.

¿Qué significa?A user with only read access can get a workflow they wrote to run on the repository's Actions runner as a trusted run, without approval. That run can receive all Actions secrets of the repository and its owner, and a GITEA_TOKEN with write access to the repository.
¿Quién está afectado?Gitea versions from 1.19.0 up to but not including 28.3.0 are in the affected range. The setup also requires a runner serving the repository, a pull request (open or merged) whose head branch is in the repository itself, and an account issued by the operator unless self-registration is enabled. Check the installed Gitea version against that range, and check whether these conditions exist for the repository.
¿Qué hacer?Upgrade Gitea to 28.3.0 or later, which is the listed fixed version. No vendor patch identifiers are given in the checked facts.
Descripción original del registro (Gitea)

Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker's workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
A runner serving the repository is required.“a runner serving the repository;”
02
A pull request whose head branch is in the repository itself (open or merged) is required.“one pull request whose head branch is in the repository itself (open or merged)”
03
An account issued by the operator is required, unless self-registration is enabled.“an account, which the operator must issue unless self-registration is enabled;”
¿Quién debe revisar?Teams running Gitea with Actions enabled and a runner serving repositories that have same-repository pull requests; affected versions 1.19.0 through 28.2.0.
No protegeDisabling fork pull requests does not fix it.
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:H
AltoBajoNinguno
IntegridadI:N
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-32h8-5xqg-h466
Fabricantehttps://blog.gitea.com/release-of-28.3.0/
Parchehttps://github.com/go-gitea/gitea/pull/40099
Parchehttps://github.com/go-gitea/gitea/pull/40117
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.