llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/obot-platform/obot

GHSA-2QCM-3GV6-2MFC

CLI login flow could be used to steal another user's API key

Parche disponible
Descargar PNG JSON
CVSS 3.1
8.1
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche2 versionesPrimer parche a -19 d de la divulgación
Exposición45 dDesde la divulgación, 6 oct 2026, 6:53 p. m.
Detección43 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir de cerca
Monitorear y programar la remediación
Estimación de Llama con el árbol SSVC de CISA a partir de vector CVSS 3.1 y la evidencia de explotación (sin evaluación oficial): sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Revisa si tu versión cae en el rango. Te espero.Esto amerita una regla de detección, por si acaso.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche v0.26.0
Monitoreo
Detectada +1
17 sept 26
6 oct 26
19 nov 26
21 nov 26
17 sept 26
4 oct 26
20 oct 26
5 nov 26
21 nov 26
FechaFaseEventoDetalle
Remediación Parche v0.26.0 github.com/obot-platform/obot · -19 d desde divulgación
Divulgación Publicada GHSA-2QCM-3GV6-2MFC divulgada · CVSS 8.1 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

Summary

In affected versions, an unauthenticated attacker could start a CLI login, send the login link to a signed-in Obot user, and collect the API key that was created when that user opened the link. The attacker could then act as that user through the Obot API, the LLM gateway, and MCP servers.

Am I affected?

You are affected if you run any Obot version before `v0.26.0`. That includes the `v0.25.x` patch releases, through `v0.25.6`, which were not patched. The attack only works if a user who is signed in to Obot, or can sign in through your identity provider, opens a link the attacker sends them.

Details

The `obot` CLI signs in through a token request: the client creates a request, the user signs in through the browser, and the client then fetches the resulting API key. The client chose the request's ID, and neither creating the request nor fetching the key required authentication or was tied to the browser that signed in. An attacker could create a request with an ID they knew, get a user to open the sign-in link for it, and then fetch the API key Obot created for that user. The attacker also chose the key's scopes and could make it never expire.

Impact

The worst case is takeover of the victim's Obot account through a long-lived API key that carries the victim's permissions, including API, LLM gateway, and MCP server access. If the victim is an admin, the attacker gets admin access. The victim only has to open one link. The attacker does not learn the victim's identity provider credentials.

Mitigation

Upgrade to v0.26.0 or later. The CLI now uses a device-code flow: Obot generates the request ID, and the signed-in user must enter the code shown by the CLI before a key is issued. After upgrading, review your users' API keys and delete any that were not created on purpose. If you cannot upgrade, blocking `POST /api/token-request` at your proxy prevents the attack, but it also disables CLI login.

Severity

CVSS v3.1 Score: 8.1/10 (High) — `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`

Credits

The Obot team would like to thank @daniel-mertz https://github.com/daniel-mertz for responsibly disclosing this issue in accordance with our security policy https://github.com/obot-platform/obot/?tab=security-ov-file.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
8.3/ 10Alto
Vector 8.3 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
github.com/obot-platform/obot< 0.26.0
0.26.0
v0.28.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/obot-platform/obot
Corregida v0.26.0 -19 d v0.28.1 no afectada
Versiones corregidas0.26.0v0.26.0
Explotación

Arsenal público

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

Referencias
Advisoryhttps://github.com/obot-platform/obot/security/advisories/GHSA-2qcm-3gv6-2mfc

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