Quick answers
- Is CVE-2026-61835 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61835 being exploited in the wild.
- How severe is CVE-2026-61835?
- High severity, with a CVSS score of 7.7, published 15 July 2026.
- Which products and versions are affected?
- directus (npm) < 12.0.0, SEMVER:introduced=0,fixed=12.0.0.
- Is there a fix for CVE-2026-61835?
- Yes. directus (npm): upgrade to 12.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61835 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61835?
- 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 12.0.0 or later
npm install directus@12.0.0
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Directus due to an incomplete IP blocklist in the file-import-from-URL feature. While the system attempts to block local network interfaces, the validation logic in 'api/src/request/is-denied-ip.ts' fails to explicitly block the literal address '0.0.0.0' (and '::' in IPv6). On Linux and macOS systems, '0.0.0.0' is treated as localhost, allowing an authenticated attacker with file-upload permissions to bypass the 'IMPORT_IP_DENY_LIST'. This results in a full-read SSRF where the server fetches content from internal services and stores the response as a downloadable file. The issue is patched in version 12.0.0.
Affected products
- Directus Directus < 12.0.0
Identifiers
- CVE-2026-61835
- GHSA-j5h6-vqc3-phqh
Timeline
- 2026-06-24: disclosed: Initial disclosure on GitHub
- 2026-07-15: advisory: NVD publication date
- 2026-07-20: advisory: GitHub Advisory reviewed and updated