llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · directus

GHSA-FQ27-7M2R-Q6VM

Manual trigger Flows can be executed by unauthenticated users

Parche disponible
Descargar PNG JSON
CVSS 3.1
6.5
Media
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -22 d de la divulgación
Exposición92 dDesde la divulgación, 20 ago 2026, 10:52 a. m.
Detección90 dDesde la divulgación hasta su ingreso al índice
Decisión estimadaSeguir
Remediar en la ventana regular de mantenimiento
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, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Parche en la próxima ventana y listo, campeón.Si tu inventario está al día, ya ganaste.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 12.2.0
Monitoreo
Detectada +1
29 jul 26
20 ago 26
18 nov 26
21 nov 26
29 jul 26
27 ago 26
25 sept 26
23 oct 26
21 nov 26
FechaFaseEventoDetalle
Remediación Parche 12.2.0 directus · -22 d desde divulgación
Divulgación Publicada GHSA-FQ27-7M2R-Q6VM divulgada · CVSS 6.5 (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

Flows with a manual trigger are intended to be executable only by an authenticated user. The authentication check in the
manual trigger handler only verified that an accountability object was present on the request. Unauthenticated API
requests are assigned a default public accountability object, which satisfied that check, so anonymous callers were not
rejected. Authorization then fell through to the permission check, which resolves an accountability object without a
user or role to the Public role.

As a result, an unauthenticated request to the public trigger endpoint (`POST /flows/trigger/:id`) could execute an
active manual Flow whenever the Flow is enabled for a collection that the Public role can read.

This is an incomplete fix of CVE-2025-53889 (GHSA-7cvf-pxgp-42fc). The guard introduced in 11.9.0 added a permission
check on the target collection and items, but did not distinguish public accountability from an authenticated identity.

Flows using the Webhook trigger are publicly triggerable by design and are not affected.

Impact

An unauthenticated attacker can execute automation that was intended to be available only to logged in users, and can
repeat that execution at will.

The consequences depend on how the Flow is configured. Operations in a Flow can be set to run with full permissions, in
which case they execute regardless of the caller's access rights. A manual Flow built for staff use can therefore give
an anonymous caller read, create, update or delete access to data that the Public role cannot reach directly. Flows can
also perform other side effecting actions, such as outbound HTTP requests, notifications and mail, which become
anonymously reachable.

Exploitation requires all of the following:

  • An active Flow with a manual trigger exists.
  • The Flow is enabled for a collection that the Public role has read access to.
  • The attacker knows the Flow's ID.
  • If the Flow requires item selection, the attacker also needs the ID of an item in that collection that the Public role

Projects that expose public content collections while using manual Flows for privileged editorial, moderation, approval,
notification or integration actions are the most exposed.

Workarounds

If upgrading is not immediately possible, any of the following reduce or remove exposure:

  • Remove Public role read access from collections that are selected on manual Flows.
  • Disable manual Flows that are attached to publicly readable collections, or convert them to a trigger type that is not
  • Review manual Flows for operations that run with full permissions and scope them down.

References

  • https://github.com/directus/directus/pull/27997
  • https://github.com/directus/directus/security/advisories/GHSA-7cvf-pxgp-42fc (CVE-2025-53889)

Credit

Reported by @sengadev

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

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:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 10.0 (muy fácil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
directus≥ 11.9.0 < 12.2.0
11.9.0
12.2.0
12.6.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmdirectus
Corregida 12.2.0 -22 d 12.6.1 no afectada
Versiones corregidas12.2.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/directus/directus/security/advisories/GHSA-fq27-7m2r-q6vm

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