Directus vulnerable to Server-Side Request Forgery On File Import

Exploitation

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

CVSS

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

EPSS

• CVE-2023-26492: 0.96% estimated exploitation activity in the next 30 days; percentile 61.57 (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 Directus versions <=9.22.4 is vulnerable to Server-Side Request Forgery (SSRF) when importing a file from a remote web server (POST to /files/import). An attacker can bypass the security controls that were implemented to patch vulnerability CVE-2022-23080 by performing a DNS rebinding attack and view sensitive data from internal servers or perform a local port scan (eg. can access internal metadata API for AWS at http://169.254.169.254 event if 169.254.169.254 is in the deny IP list). Details DNS rebinding attacks work by running a DNS name server that resolves two different IP addresses when a domain is resolved simultaneously. This type of attack can be exploited to bypass the IP address deny list validation that was added to /api/src/services/file.ts for the function importOne to mitigate the previous SSRF vulnerability CVE-2022-23080. The validation in /api/src/services/file.ts first checks if the resolved IP address for a domain name does not a resolve to an IP address…

Published by the source

3 Mar 2023, 23:07 UTC

Last modified by the source

8 Nov 2023, 04:12 UTC

Source last checked

26 Oct 2026, 12:21 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-j3rg-3rgm-537h

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-j3rg-3rgm-537h

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

# Patch Next advisory brief: CVE-2023-26492

Advisory: Directus vulnerable to Server-Side Request Forgery On File Import
IDs: CVE-2023-26492, GHSA-j3rg-3rgm-537h
Record: https://patchnext.com/advisories/cve-2023-26492 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: directus 9.23.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm directus: affected < 9.23.0; fixed in 9.23.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-j3rg-3rgm-537h (OSV record GHSA-j3rg-3rgm-537h lists affected ranges: npm directus >=0 <9.23.0 (fixed))
- Verified: https://github.com/advisories/GHSA-j3rg-3rgm-537h (GitHub-reviewed advisory GHSA-j3rg-3rgm-537h lists affected ranges: npm directus >=0 <9.23.0)

Commands are suggestions: review each one before running it.