# CVE-2026-129239: Directus: Share update allows reassigning user_created and role

> Authenticated Directus users with share update permission can reassign share items to administrator roles, exposing data beyond share permissions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-7h45-q5jx-7r87

## What is CVE-2026-129239?

CVE-2026-129239 is a medium-severity privilege escalation vulnerability in directus, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.3.1, Directus allows an authenticated non-admin with update permission on directus_shares to modify user_created, role, item, and collection on an existing owned share because authorization checks the pre-update row and does not revalidate the merged row. The update path does not force user_created to the acting user or rerun share access checks when item or collection changes. Setting user_created and role to administrator identifiers causes guest share authentication to derive administrator accountability from both fields, exposing data reachable from the shared item beyond the owner and share role permissions. The issue requires update permission on directus_shares, an item the account can share, and knowledge of administrator user and role identifiers, and it does not issue an administrator token or provide write or availability impact. This issue is fixed in version 12.3.1.

Weakness: CWE-863 (Incorrect Authorization), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-129239?

1 open source package ship an affected version, including directus.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `directus` | npm | `pkg:npm/directus` | All versions | 12.3.1 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `directus` | 12.3.1 |

## How do I fix CVE-2026-129239?

Upgrade directus to 12.3.1 or later.

## Is CVE-2026-129239 being exploited?

There is no known exploitation of CVE-2026-129239 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129239 and fix it if it is affected.

What it is: CVE-2026-129239 is a medium-severity privilege escalation vulnerability in directus, published on 16 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129239 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- directus (npm): affected all versions; fixed in 12.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129239/ (Markdown: https://insights.sbomify.com/CVE-2026-129239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129239
- OSV: https://osv.dev/vulnerability/CVE-2026-129239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129239/
Summaries are generated and may contain mistakes; the official description above is the record.
