# CVE-2026-61836: Directus: Authorization-dependent response served from unsegmented cache key

> Attackers can access permission-filtered cached data intended for other users due to incomplete cache key derivation when response caching is enabled.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-c6w9-5g5j-jh2p

## What is CVE-2026-61836?

CVE-2026-61836 is a high-severity missing authorization vulnerability in Monospace Directus, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, 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.0.0, when response caching is enabled, the cache-key derivation in api/src/utils/get-cache-key.ts includes version, path, query, and accountability.user but omits authorization context such as share, role, roles, admin, app, and policies. Directus share tokens and anonymous requests can both reduce to user null, so different shares or anonymous clients requesting the same URL and query can receive a permission-filtered cached response without permission re-evaluation. This issue is fixed in version 12.0.0.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-524 (Use of Cache Containing Sensitive Information)

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

2 open source packages ship an affected version, including directus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `directus` | npm | All versions | 12.0.0 |
| `directus` | npm | All versions | 12.0.0 |

Products: Monospace Directus.

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

Upgrade directus to 12.0.0 or later.

## Is CVE-2026-61836 being exploited?

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

## Other vulnerabilities in Monospace Directus

- [CVE-2022-26969](https://insights.sbomify.com/CVE-2022-26969/): Insecure default value for CORS configuration (critical 9.8)
- [CVE-2025-55746](https://insights.sbomify.com/CVE-2025-55746/): Directus allows unauthenticated file upload and file modification due to lacking input sanitization (critical 9.3)
- [CVE-2026-35408](https://insights.sbomify.com/CVE-2026-35408/): Directus is Missing Cross-Origin Opener Policy (high 8.7)
- [CVE-2025-30353](https://insights.sbomify.com/CVE-2025-30353/): Directus's webhook trigger flows can leak sensitive data (high 8.6)
- [CVE-2026-39942](https://insights.sbomify.com/CVE-2026-39942/): Directus has a Path Traversal and Broken Access Control in File Management API (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61836 is a high-severity missing authorization vulnerability in Monospace Directus, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61836 in the wild and no public exploit code.

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

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

## Sources

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

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