Quick answers
- Is CVE-2026-35441 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35441 being exploited in the wild.
- How severe is CVE-2026-35441?
- Medium severity, with a CVSS score of 6.5, published 6 April 2026.
- Which products and versions are affected?
- directus (npm) SEMVER:introduced=0,fixed=11.17.0.
- Is there a fix for CVE-2026-35441?
- Yes. directus (npm): upgrade to 11.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35441 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35441?
- 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.17.0 or later
npm install directus@11.17.0
Technical details
Directus GraphQL endpoints (/graphql and /graphql/system) fail to deduplicate resolver invocations within a single request. An authenticated attacker can use GraphQL aliasing to repeat expensive relational queries multiple times in one request, bypassing existing token and depth limits which are applied per alias rather than per request. Because rate limiting is disabled by default, this results in linear multiplication of database load, leading to CPU, memory, and I/O exhaustion. The vulnerability is rooted in CWE-400 and CWE-770 and is resolved in version 11.17.0 by implementing a request-scoped resolver deduplication mechanism.
Affected products
- Directus Directus < 11.17.0
Identifiers
- CVE-2026-35441
- GHSA-ph52-67fq-75wj
Timeline
- 2026-04-02: advisory: Vendor advisory published on GitHub
- 2026-04-06: disclosed: CVE published