CVE-2026-129239: Directus: Share update allows reassigning user_created and role
Summary A non-admin user who can update their own shares can reassign a share's creator (usercreated), 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.
Published Nov 16, 2026
Affected packages
directus
- Ecosystem
- npm
- Affected
- < 12.3.1
- Fixed in
- 12.3.1
- Check
npm ls directus
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 fordirectus_sharesthat 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.
Credited to Binary-Spec.
References
- https://github.com/directus/directus/security/advisories/GHSA-7h45-q5jx-7r87
- https://nvd.nist.gov/vuln/detail/CVE-2026-129239
- https://github.com/directus/directus/pull/28145
- https://github.com/directus/directus/commit/5869c06f6997af0d2f13b39b3d19297dd2ed2f65
- https://github.com/directus/directus/releases/tag/v12.3.1
- https://github.com/advisories/GHSA-7h45-q5jx-7r87
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-61835
Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
high7.7Jul 20, 2026CVE-2026-61836
Directus: Authorization-dependent response served from unsegmented cache key
high8.6Jul 20, 2026CVE-2026-35408
Directus: Missing Cross-Origin Opener Policy
high8.7Apr 4, 2026CVE-2026-35409
Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
high7.7Apr 4, 2026CVE-2026-35410
Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
medium6.1Apr 4, 2026CVE-2026-35411
Directus: Open Redirect in Admin 2FA Setup Page
medium4.3Apr 4, 2026
