llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · directus

GHSA-7H45-Q5JX-7R87

Directus: Share update allows reassigning user_created and role

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -83 d de la divulgación
Exposición3 dDesde la divulgación, 16 nov 2026, 5:25 p. m.
Detección2 hDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada +1
Explotación
Remediación
Parche 12.3.1
Monitoreo
Detectada +1
25 ago 26
16 nov 26
17 nov 26
20 nov 26
25 ago 26
16 sept 26
8 oct 26
30 oct 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 12.3.1 directus · -83 d desde divulgación
Divulgación Publicada GHSA-7H45-Q5JX-7R87 divulgada
Divulgación Modificada Última actualización del registro
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 non-admin user who can update their own shares can reassign a share's creator (`user_created`), `role`, `item`, and `collection` fields after the share is created. The update is authorized against the row as it existed before the change, and the resulting row is never revalidated, so these fields can be set to values the user would not be permitted to assign when creating a share. By reassigning both `user_created` and `role` to an administrator the share's effective permissions get elevated.

This is a server-side authorization gap in the share update path. It does not by itself produce an administrator token. It re-opens a previously patched privilege-escalation surface on the effective permissions of a share.

Prerequisites
  • An authenticated non-admin account that holds update permission on `directus_shares`. This is not part of the baseline app-access grant, which is read-only on a user's own shares, but it is part of the recommended defaults permission template for `directus_shares` that instances commonly apply so the share feature is usable.
  • An item the account is allowed to share.
  • Knowledge of an administrator user and role identifier to assign. In the reported case these were read from a relation on the shareable item using ordinary read permissions.
Details

The recommended default permission for updating `directus_shares` selects rows where the caller is the creator and permits writes to the full field set, including the creator, role, item, and collection. The ownership filter is evaluated only against the row as it exists before the update, so an owned share passes the check. The merged row is never re-checked to decide whether the caller may assign the new values.

Two guards that are enforced when a share is created are absent on update. On create, the creator is forced to the acting user, and a share-access check is run against the target item to confirm the caller is allowed to share it. On update, the supplied creator value is stored as given and no equivalent share-access check is run against the new item or collection, so both the creator and the shared target can be repointed to values the caller was never authorized to set. The read-only marking on the creator field in the schema is a Data Studio UI hint and does not constrain writes through the API.

When a guest authenticates through the share, Directus derives one accountability from the share's creator and another from the share's role, and applies administrator reach only when both resolve to an administrator. After both fields are reassigned to an administrator, both inputs resolve to administrator and the share is evaluated with full-schema reach starting from the shared item. This is the bypass of the CVE-2025-24353 intersection, which assumed the creator and selected role remain trustworthy after creation, when in fact both are mutable together through update.

Impact

Improper authorization (CWE-863) and improper privilege management (CWE-269). A non-admin can raise the effective permissions of a share they own beyond both their own permissions and the share role's permissions, exposing data reachable from the shared item that neither principal should be able to expose. The direct impact is to confidentiality. This issue alone does not grant write or availability impact.

Versiones

Rangos afectados

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

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmdirectus
Corregida 12.3.1 -83 d 12.6.1 no afectada
Versiones corregidas12.3.1
Explotación

Arsenal público

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

Referencias
Advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-129239
Otrahttps://github.com/directus/directus/security/advisories/GHSA-7h45-q5jx-7r87
Otrahttps://github.com/directus/directus/pull/28145
Otrahttps://github.com/directus/directus/commit/5869c06f6997af0d2f13b39b3d19297dd2ed2f65
Otrahttps://github.com/directus/directus
Otrahttps://github.com/directus/directus/releases/tag/v12.3.1

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