NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Directus: Share update allows reassigning user_created and roleGHSA-7h45-q5jx-7r87

MEDIUMFix: directus/directus#28145

GHSA-7h45-q5jx-7r87 is a medium-severity (CVSS 6.5) Improper Privilege Management vulnerability in directus. A fix is available for directus — see the affected versions and patch details below.

Also known asCVE-2026-129239
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7h45-q5jx-7r87.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

12other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
directusnpm
34Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdirectusall versions12.3.1npm install directus@12.3.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for directus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update directus to 12.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7h45-q5jx-7r87 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### 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 itsel
O3 Security · Impact-Aware SCA

Is GHSA-7h45-q5jx-7r87 in your dependencies?

Find it across npm, including transitive dependencies.

Directus: Share update allows reassigning user_created…