Vulnerability in Directus (CVE-2026-35410)
Summary
Vulnerability in Directus (CVE-2026-35410). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 11.16.1 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 11.16.1, an open redirect vulnerability exists in the login redirection logic. The isLoginRedirectAllowed function fails to correctly identify certain malformed URLs as external, allowing attackers to bypass redirect allow-list validation and redirect users to arbitrary external domains upon successful authentication. This vulnerability is fixed in 11.16.1.
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-35410 has been found in Directus.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade Directus to 11.16.1 or later.
If unsure, ask your IT team or search "Directus CVE-2026-35410" on the vendor's site.
CVE-2026-35410 (Directus) — CWE-184 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 11.16.1 — 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-184) exists in Directus.
Check the vendor advisory for the affected versions of Directus.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 11.16.1.
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 11.16.1ステージング環境で 11.16.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov