Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 4 April 2026.
- Which products and versions are affected?
- directus (npm) SEMVER:introduced=0,fixed=11.17.0.
- Is there a fix for This vulnerability?
- 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 This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- 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
The vulnerability exploits GraphQL alias specification behavior, where each alias in a single query normally resolves independently. Directus failed to deduplicate resolver invocations within a single request, causing the health check resolver to execute fully for each alias despite identical arguments. The health check resolver performs expensive operations including database connectivity verification, cache checks, storage writes, and SMTP verification. An unauthenticated attacker can craft a request with numerous aliases invoking the same resolver, amplifying resource consumption significantly from a single HTTP request. The fix introduces request-scoped resolver deduplication so identical invocations share results, eliminating the amplification factor. This was patched in version 11.17.0.
Affected products
- Directus Directus before 11.17.0
Timeline
- 2026-04-04: disclosed
- 2026-04-04: patched: version 11.17.0