Vulnerability in directus (CVE-2026-61836)
Summary
Vulnerability in directus (CVE-2026-61836). Confidential information can be exposed externally. Exploitable via version. Mitigation: upgrade to 12.0.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61836 has been found in directus.
Attackers can target a specific entry point like version over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade directus to 12.0.0 or later.
If unsure, ask your IT team or search "directus CVE-2026-61836" on the vendor's site.
CVE-2026-61836 (directus) — CWE-524 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: version / path / query / accountability.user
Patched: 12.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-524) exists in directus. Attackers reach the vulnerable code path via version without authentication.
Check the vendor advisory for the affected versions of directus. Attack surface: version / path / query / accountability.user.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 12.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'directus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'directus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
directusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade directus to 12.0.0ステージング環境で 12.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com