# CVE-2026-35409: Directus SSRF protection bypass in File Import

Source: https://junglewise.ai/threats/cve-2026-35409-directus-ssrf-protection-bypass-in-file-import  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-06. Updated: 2026-07-24  
License: CC BY 4.0 with a link back

CVE-2026-35409 · Severity: high · CVSS 7.7 · Published 2026-04-06

Directus, a platform for managing database content and APIs, contains a security flaw in its file import feature. An attacker can bypass security filters to force the server to make requests to internal systems, such as private databases or cloud metadata services. This could lead to the exposure of sensitive internal data or administrative credentials.

Technologies: [directus (npm)](https://junglewise.ai/threats/technologies/directus). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-35409 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-35409 being exploited in the wild.

**How severe is CVE-2026-35409?** High severity, with a CVSS score of 7.7, published 6 April 2026.

**Which products and versions are affected?** directus (npm) SEMVER:introduced=0,fixed=11.16.0.

**Is there a fix for CVE-2026-35409?** Yes. directus (npm): upgrade to 11.16.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-35409 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-35409?** Check whether you run directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- directus (npm): upgrade to 11.16.0 or later

  ```sh
  npm install directus@11.16.0
  ```


## Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Directus due to improper normalization of IP addresses in the file import component. The application implements an IP deny-list to prevent requests to internal/private network ranges, but the validation logic fails to account for IPv4-Mapped IPv6 address notation (e.g., ::ffff:127.0.0.1). An authenticated attacker (or unauthenticated if public permissions are enabled) can bypass the deny-list to reach internal services, databases, or cloud instance metadata services (IMDS). The underlying HTTP client and OS resolve these mapped addresses to their private IPv4 targets despite the bypass. The issue is resolved in version 11.16.0 by adding a normalization step prior to validation.

## Affected products

- Directus Directus < 11.16.0

## Identifiers

- CVE-2026-35409
- GHSA-wv3h-5fx7-966h

## Timeline

- 2026-04-02: advisory: GitHub Security Advisory published by vendor
- 2026-04-06: disclosed: CVE published to NVD
- 2026-04-06: patched: Fix released in version 11.16.0

## References

- [https://github.com/directus/directus/security/advisories/GHSA-wv3h-5fx7-966h](https://github.com/directus/directus/security/advisories/GHSA-wv3h-5fx7-966h)

## Related threats

- [Directus authorization bypass via unsegmented response cache key](https://junglewise.ai/threats/cve-2026-61836-directus-authorization-bypass-via-unsegmented-response-cache-key)
- [Directus SSRF bypass in file import via 0.0.0.0 address](https://junglewise.ai/threats/cve-2026-61835-directus-ssrf-bypass-in-file-import-via-0-0-0-0-address)
- [Directus sensitive information disclosure via aggregate queries](https://junglewise.ai/threats/cve-2026-35442-directus-sensitive-information-disclosure-via-aggregate-queries)
- [Directus resource exhaustion via GraphQL alias amplification](https://junglewise.ai/threats/cve-2026-35441-directus-resource-exhaustion-via-graphql-alias-amplification)
- [Directus GraphQL introspection bypass in system endpoint](https://junglewise.ai/threats/cve-2026-35413-directus-graphql-introspection-bypass-in-system-endpoint)