MEDIUMCVSS v3.1 6.5Vulnerability

CVE-2026-129239

### 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

Properties

Summary
Directus: Share update allows reassigning user_created and role
Severity
medium
Nvd fetched at
2026-11-16T22:44:16.771339+00:00
Cvss score
6.5
Cvss severity
MEDIUM
Retrieved at
2026-11-16T22:45:19+00:00
Ghsa published
2026-11-16T22:25:53Z
Source url
https://github.com/advisories/GHSA-7h45-q5jx-7r87
Ghsa updated
2026-11-16T22:25:54Z
Ghsa id
GHSA-7h45-q5jx-7r87
Last source
GitHub Advisory Database
Score
6.5
Cvss version
3.1
Cve id
CVE-2026-129239
Cvss vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
First seen by Signal
2026-11-16T18:35:21+00:00
Is ghsa only
false
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Published at
2026-11-16T17:17:31.633
Last modified
2026-11-16T18:17:30.063

Related Entities (4)

HAS_WEAKNESS (2)

AFFECTS (1)

→[Software]npm/directus

VULNERABLE_TO (1)

←[Software]npm/directus

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-129239 (CVSS v3.1 6.5) — Ninja Signal Threat Intelligence | Ninja Signal