Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-35409: 0.34% estimated exploitation activity in the next 30 days; percentile 27.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details Directus implements an IP deny-list to prevent server-side requests to internal/private network ranges. The validation logic failed to normalize IPv4-Mapped IPv6 addresses (e.g., the IPv6 representation of 127.0.0.1) before checking them against the deny-list. Because the deny-list check did not recognize these mapped addresses as equivalent to their IPv4 counterparts, an attacker could bypass the restriction while the underlying HTTP client and operating system still resolved and connected to the intended private target. This has been fixed by adding a normalization step that converts IPv4-Mapped IPv6 addresses to their canonical IPv4 form prior to validation. Impact An authenticated user (or an unauthenticated user if…

Published by the source

4 Apr 2026, 06:10 UTC

Last modified by the source

7 Apr 2026, 14:38 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wv3h-5fx7-966h

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wv3h-5fx7-966h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35409

Advisory: Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
IDs: CVE-2026-35409, GHSA-wv3h-5fx7-966h
Record: https://patchnext.com/advisories/cve-2026-35409 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: directus 11.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm directus: affected < 11.16.0; fixed in 11.16.0

## Suggested inspection (read-only)
- `npm ls directus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on directus.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wv3h-5fx7-966h (OSV record GHSA-wv3h-5fx7-966h lists affected ranges: npm directus >=0 <11.16.0 (fixed))
- Verified: https://github.com/advisories/GHSA-wv3h-5fx7-966h (GitHub-reviewed advisory GHSA-wv3h-5fx7-966h lists affected ranges: npm directus >=0 <11.16.0)

Commands are suggestions: review each one before running it.