SSRF (Server-Side Request Forgery) in Directus (CVE-2026-35409)
Summary
SSRF in Directus (CVE-2026-35409). Confidential information can be exposed externally. Mitigation: upgrade to 11.16.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 11.16.0, a Server-Side Request Forgery (SSRF) protection bypass has been identified and fixed in Directus. The IP address validation mechanism used to block requests to local and private networks could be circumvented using IPv4-Mapped IPv6 address notation. This vulnerability is fixed in 11.16.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-35409 has been found in Directus.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade Directus to 11.16.0 or later.
If unsure, ask your IT team or search "Directus CVE-2026-35409" on the vendor's site.
CVE-2026-35409 (Directus) — CWE-918 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Patched: 11.16.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.
SSRF (CWE-918) exists in Directus.
Check the vendor advisory for the affected versions of Directus.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 11.16.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 11.16.0ステージング環境で 11.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov