Directus: SSRF Protection Bypass via 0.0.0.0 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-61835: 0.41% estimated exploitation activity in the next 30 days; percentile 35.07 (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 The SSRF protection on Directus's file-import-from-URL feature can be bypassed using the address 0.0.0.0. While 127.0.0.1 and other internal addresses are denied, 0.0.0.0 is not added to the blocklist. On Linux and macOS, connecting to 0.0.0.0 reaches localhost, so an authenticated user with file-upload rights can make the server fetch internal services and retrieve the response as a downloadable file (full-read SSRF). Affected Versions - Affected: Directus <= 12.0.0 (confirmed on directus/directus:latest, v11.17.3, with default configuration) - Patched: Directus = 12.0.0 Details Directus uses a deny-list config, IMPORTIPDENYLIST, whose default value is ['0.0.0.0', '169.254.169.254']. The issue is in how api/src/request/is-denied-ip.ts processes this list. When it encounters the entry 0.0.0.0, it treats it as a special keyword meaning "block all local network interfaces," but it never blocks the literal address 0.0.0.0 itself. The handler sets the network-interface flag and…

Published by the source

20 Jul 2026, 21:47 UTC

Last modified by the source

20 Jul 2026, 22:00 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j5h6-vqc3-phqh

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j5h6-vqc3-phqh

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

# Patch Next advisory brief: CVE-2026-61835

Advisory: Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
IDs: CVE-2026-61835, GHSA-j5h6-vqc3-phqh
Record: https://patchnext.com/advisories/cve-2026-61835 (revision 2, source checked 26 Oct 2026, 12:57 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 12.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm directus: affected < 12.0.0; fixed in 12.0.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-j5h6-vqc3-phqh (OSV record GHSA-j5h6-vqc3-phqh lists affected ranges: npm directus >=0 <12.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-j5h6-vqc3-phqh (GitHub-reviewed advisory GHSA-j5h6-vqc3-phqh lists affected ranges: npm directus >=0 <12.0.0)

Commands are suggestions: review each one before running it.