llamaCVEVulnerability Intelligence
/
Gitea

CVE-2026-118395

Gitea access control bypass in repository and org creation

An attacker with a public-only token can create private repositories, organizations, and template-based repos.

Default setupsSin parche publicadoaccess control bypass
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/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: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, 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-118395 divulgada · CVSS 7.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. A personal access token limited to public resources could still create private repositories, create private organizations, and generate private repositories from templates through several API endpoints, bypassing a fix in a recent release.

Affects Gitea before 28.3.0 when a personal access token has the public-only restriction plus write:repository and write:organization scopes, and the account can create repositories in the target organization. Fixed in 28.3.0.

¿Qué significa?The public-only restriction on a personal access token is not enforced when creating repositories and organization repositories. The token can therefore create repositories that the restriction was meant to block.
¿Quién está afectado?Gitea versions up to and including 28.2.0 are affected. The version is shown on the server's version information page. The bug needs a personal access token with public-only, write:repository, and write:organization scopes, and an account with create-repository permission on the target organization; owning an organization it created is enough. Token scopes are listed in the account's applications settings.
¿Qué hacer?Upgrade Gitea to 28.3.0 or later, which is the fixed version.
Descripción original del registro (Gitea)

Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and `POST /api/v1/repos/{owner}/{repo}/generate` still accepted such tokens. A holder of a public-only token with the needed write scopes could create private repositories in organizations where the token's owner may create repositories, create private organizations, and generate private repositories from templates. The token still could not read the private repositories it created.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Gitea version 1.27.3 or earlier, up to and including 28.2.0 (fixed in 28.3.0)“Affected versions <= 28.2.0”
02
The attacker holds a personal access token with the public-only restriction plus write:repository and write:organization scopes (write:user also added in the PoC)“A PAT whose normalized scopes include public-only , write:repository , and write:organization .”
03
The account has create-repository permission on the target organization (owning an org it created is sufficient)“That account has CanCreateOrgRepo on the target org.”
¿Quién debe revisar?Teams running Gitea 28.2.0 or earlier (including 1.27.x), especially self-hosted instances with open registration and organization creation enabled
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:N
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≤ 28.2.0
gitea.dev< 28.3.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-x5v4-836g-f95x
Fabricantehttps://blog.gitea.com/release-of-28.3.0/
Parchehttps://github.com/go-gitea/gitea/pull/39690
Parchehttps://github.com/go-gitea/gitea/pull/39853
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.