llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · directus

GHSA-95F8-MVW7-GPJ9

File uploads can write into the extensions directory, leading to code execution in overlapping storage configurations

Parche disponible
Descargar PNG JSON
CVSS 3.1
6.6
Media
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -23 d de la divulgación
Exposición21 dDesde la divulgación, 30 oct 2026, 10:00 a. m.
Detección19 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.
Las PoC crecen rápido, como las llamas bebé.Si sale un exploit, la subo de categoría. Atento.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Parche 12.5.0
Monitoreo
Detectada +1
7 oct 26
30 oct 26
18 nov 26
21 nov 26
7 oct 26
18 oct 26
30 oct 26
10 nov 26
21 nov 26
FechaFaseEventoDetalle
Remediación Parche 12.5.0 directus · -23 d desde divulgación
Divulgación Publicada GHSA-95F8-MVW7-GPJ9 divulgada · CVSS 6.6 (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

A user who is allowed to set `storage` and `filename_disk` when creating files could upload into the directory Directus loads extensions from, whenever that directory was reachable through a configured storage location. Directus executes extension code inside the server process, so this leads to server-side code execution. With `EXTENSIONS_AUTO_RELOAD` enabled, overwriting the entrypoint of an already loaded extension runs the uploaded code immediately. Otherwise it runs on the next restart or extension reload.

Details

The file upload path wrote to whichever storage location and `filename_disk` the payload specified, as long as the path stayed inside the storage root. It did not check whether that path was also part of the extensions namespace. Two configurations expose this:

  • A local storage location whose root contains `EXTENSIONS_PATH`, for example `STORAGE_LOCAL_ROOT=/directus/uploads` with `EXTENSIONS_PATH=/directus/uploads/extensions`. An upload with `filename_disk=extensions/<name>/index.mjs` overwrites that extension's entrypoint on disk.
  • `EXTENSIONS_LOCATION` pointing at a storage location that is also available for uploads. An upload into `EXTENSIONS_PATH` on that location places a new extension that is synced and loaded on the next start.

An earlier guard added for this class compared the storage-root-prefixed path against the location-relative `EXTENSIONS_PATH` for local drivers, so it did not trigger for the second configuration when the extensions location used the local driver.

The default configuration is not affected. `storage` and `filename_disk` are not writable by non-admin roles unless an administrator grants them explicitly, the default local layout keeps `./uploads` and `./extensions` as sibling directories, and `EXTENSIONS_LOCATION` is unset by default.

Impact

An authenticated user whose role has create (or update) permission on `directus_files` with write access to the `storage` and `filename_disk` fields can execute arbitrary JavaScript in the Directus process, on instances where an upload-writable storage location overlaps the extensions directory. That gives access to the process environment, any files and internal services the Directus process can reach, and full control over the application.

Workarounds

a. Do not grant non-admin roles write access to the `storage` and `filename_disk` fields of `directus_files`.
b. Keep `EXTENSIONS_PATH` outside every storage location root, and do not use the storage location set as `EXTENSIONS_LOCATION` for regular uploads.
c. Do not enable `EXTENSIONS_AUTO_RELOAD` in production.

Credits

Reported by kamil-sawicki https://github.com/kamil-sawicki

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:H
BajaAlta
PrivilegiosPR:H
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
3.6/ 10Bajo
Vector 3.6 (difícil) · sin evidencia de explotación.
Versiones

Rangos afectados

Afectada Corregida Última
directus< 12.5.0
12.5.0
12.6.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmdirectus
Corregida 12.5.0 -23 d 12.6.1 no afectada
Versiones corregidas12.5.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-95f8-mvw7-gpj9

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