# CVE-2026-35409: Directus has a SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import

> Attackers can bypass SSRF protections in Directus file imports using IPv4-mapped IPv6 addresses to access internal networks.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wv3h-5fx7-966h

## What is CVE-2026-35409?

CVE-2026-35409 is a high-severity server-side request forgery vulnerability in Monospace Directus, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


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

Products: Monospace Directus.

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

Upgrade directus to 11.16.0 or later.

## Is CVE-2026-35409 being exploited?

There is no known exploitation of CVE-2026-35409 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-2026-61836](https://insights.sbomify.com/CVE-2026-61836/): Directus: Authorization-dependent response served from unsegmented cache key (high 8.6)
- [CVE-2025-30353](https://insights.sbomify.com/CVE-2025-30353/): Directus's webhook trigger flows can leak sensitive data (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35409 is a high-severity server-side request forgery vulnerability in Monospace Directus, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35409 in the wild and no public exploit code.

Affected packages and fixed versions:
- directus (npm): affected all versions; fixed in 11.16.0
- directus (npm): affected all versions; fixed in 11.16.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-35409/ (Markdown: https://insights.sbomify.com/CVE-2026-35409/index.md)
```

## Sources

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

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