llamaCVEVulnerability Intelligence
/
Gitea

CVE-2026-119627

Gitea access control bypass in user profile and feed pages

Attackers with a public-only token can view hidden accounts' profiles and public activity but cannot modify them.

Specific setups onlySin parche publicadoaccess control bypass
Descargar PNG JSON
CVSS 3.1
4.3
Media
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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ón11 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-119627 divulgada · CVSS 4.3 (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, a self-hosted Git service, is affected: its web profile and RSS/Atom feed pages can be read by someone using a public-only access token, even for users and organizations whose visibility is limited. An attacker holding such a token could see the existence, profile details, and public activity of those hidden accounts, though they could not modify anything.

Gitea before 28.3.0 lets a holder of a public-only personal access token using HTTP Basic auth read limited-visibility user and organization profiles. Fixed in 28.3.0.

¿Qué significa?A public-only token can discover and read profiles of users and organizations whose visibility is limited, which anonymous callers correctly receive as 404. The exposed data includes existence, display name, description, public repository names and public activity, and the HTML profile also shows starred or watched repositories, followers and organization memberships. The access is read-only.
¿Quién está afectado?Gitea versions before 28.3.0 in the default configuration are affected, since RSS/Atom feeds are enabled by default. The setup also requires a personal access token scoped to public-only and used with HTTP Basic auth. To check the version, run gitea --version on the server.
¿Qué hacer?Upgrade Gitea to 28.3.0 or later, which contains the fix for this vulnerability.
Descripción original del registro (Gitea)

The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without considering the `public-only` restriction of the personal access token used to authenticate. Any user holding a public-only token could send it over HTTP Basic authentication to read the profile and activity feed of limited-visibility users and organizations, which are hidden from anonymous visitors and refused on the equivalent API routes. The disclosure covers existence, profile metadata and public activity; it does not grant write access.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Viewer holds a personal access token scoped public-only and authenticates with HTTP Basic auth“A holder of a public-only scoped PAT can discover and read the profile”
02
Target is a limited-visibility user or organization“Anonymous callers correctly receive 404 for these users”
03
Default configuration is affected; RSS/Atom feeds are enabled by default“Default configuration is affected; EnableFeed is true by default.”
¿Quién debe revisar?Operators of Gitea instances on Go module code.gitea.io/gitea 1.27.0 through 1.27.3, and anyone issuing public-only personal access tokens on Gitea.
No protegeFixing CVE-2026-56443 alone leaves the web profile route open.
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:L
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-5j4v-rwqr-vpq7
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
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.