# CVE-2026-132136: Directus Share Login Service shares.ts getSecret authorization


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-5x8m-h7mg-2xwr

## What is CVE-2026-132136?

CVE-2026-132136 is a medium-severity vulnerability in Directus, published on 18 Nov 2026. 

### Official description

A weakness has been identified in Directus up to 12.6.1. Affected by this issue is the function getSecret of the file api/src/services/shares.ts of the component Share Login Service. This manipulation causes incorrect authorization. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Directus.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:directus:directus:*:*:*:*:*:*:*:*` from 12.6.0 up to 12.6.0
- `cpe:2.3:a:directus:directus:*:*:*:*:*:*:*:*` from 12.6.1 up to 12.6.1

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

No fix has been published for CVE-2026-132136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-132136 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132136 is a medium-severity vulnerability in Directus, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132136 in the wild and no public exploit code.

Affected product: Directus. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-132136/ (Markdown: https://insights.sbomify.com/CVE-2026-132136/index.md)
```

## Sources

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

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