llamaCVEVulnerability Intelligence
/
flowintel

CVE-2026-133658

flowintel auth bypass in Matrix relay allows privilege escalation

Low-privilege users can edit restricted data and impersonate the Matrix bot by copying its profile name and email.

Parche disponibleauthorization bypass
Descargar PNG JSON
CVSS 4.0
6.3
Media
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N Fuente: CNA
ExplotaciónSin evidenciaSSVC: ninguna · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión4.1.0
Exposición1 dDesde la divulgación, 20 nov 2026, 5:55 a. m.
Detección7 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Si sale un exploit, la subo de categoría. Atento.Revisa tus logs de la semana con la lupa.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +1
Fuente: ENISA EUVD
Verificada
05:55 a. m.
06:02 a. m.
11:23 a. m.
12:22 p. m.
07:09 a. m.
05:55 a. m.
12:13 p. m.
06:32 p. m.
12:50 a. m.
07:09 a. m.
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-133658 divulgada · CVSS 6.3 (CNA)
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: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 20 nov 2026

Flowintel's Matrix relay integration has an authorization flaw that lets an attacker with a low-privileged account, reached remotely over the network, make write changes to cases, tasks, calendar events, templates, and user directory entries that their restricted role should block. Because the relay is recognized by editable profile name and email fields, an ordinary user who sets those fields to match the bot can impersonate the trusted relay and gain its elevated privileges.

Descripción original del registro (CIRCL)

Flowintel contains a privilege escalation vulnerability in its Matrix relay (bot) integration. When the relay forwarded API requests on behalf of a represented user, the authorization and permission checks evaluated the relay bot's elevated role while the request handlers acted as the lower-privileged represented user. This mismatch allowed users with restricted roles (e.g., Read Only) to perform write operations, directory lookups, calendar modifications, assignment changes, template creation, and import actions they were not authorized to perform. Additionally, relay authority was determined by matching editable user profile fields (name and email) rather than a protected, non-spoofable identifier. An ordinary user who modified their profile to match the expected bot name could be recognized as the trusted relay, enabling impersonation of the bot and potential access to its elevated privileges. Preconditions: - A valid Flowintel user account with a restricted role (e.g., Read Only) - Access to the Matrix relay integration or the ability to send API requests with the relay's API key and a MATRIX-ID header - For the impersonation vector: ability to edit one's own profile name fields Security impact: - Unauthorized write operations by users with read-only or otherwise restricted permissions - Potential impersonation of the trusted relay bot by ordinary users - Bypass of organization-level access controls and role-based restrictions - Unauthorized modification of cases, tasks, calendar events, templates, and user directory entries Affected versions: Flowintel prior to 4.1.0

Vector CVSS 4.0

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
Requisitos de ataqueAT:N
NingunoPresentes
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaPasivaActiva
Confid. (sistema)VC:N
AltoBajoNinguno
Integridad (sistema)VI:N
AltoBajoNinguno
Disponib. (sistema)VA:N
AltoBajoNinguno
Confid. (posterior)SC:N
AltoBajoNinguno
Integridad (posterior)SI:H
AltoBajoNinguno
Disponib. (posterior)SA: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
flowintel< 4.1.0
4.1.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
flowintel
Corregida 4.1.0 — —
Versiones corregidas4.1.0
Explotación

Arsenal público

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

Registro
EscenarioGENERALCIRCL
solutionThe fix introduces a protected, non-editable is_bot database marker to identify trusted relay accounts, replacing the previous reliance on editable name and email fields. The user resolution function now returns the same principal for both authentication/permission checks and request handlers, ensuring that a represented user's actual role governs all operations. Relay requests without a valid MATRIX-ID, bot-to-bot requests, and ordinary API keys carrying a MATRIX-ID header are all refused. New bot accounts are assigned the Read Only role instead of Admin. Only administrators can edit or delete registered bot accounts, preventing OrgAdmins from resetting bot credentials. An operator script (bin/register_matrix_bot.py) provides explicit, ID-based bot registration without relying on profile fields.CIRCL
Referencias
Parchehttps://github.com/flowintel/flowintel/commit/48e9e1b847ecd22da11e70829f1ecfaa0df3791d

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