CVE-2026-35441: Directus: GraphQL Alias Amplification Denial of Service Due to Missing Query Cost/Complexity Limits
Summary Directus' GraphQL endpoints (/graphql and /graphql/system) did not deduplicate resolver invocations within a single request. An authenticated user could exploit GraphQL aliasing to repeat an expensive relational query many times in a single request, forcing the server to execute a large number of independent complex database queries concurrently, multiplying database load linearly with the number of aliases.
Published Apr 4, 2026 · Updated Apr 7, 2026
Affected packages
directus
- Ecosystem
- npm
- Affected
- < 11.17.0
- Fixed in
- 11.17.0
- Check
npm ls directus
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Directus' GraphQL endpoints (/graphql and /graphql/system) did not deduplicate resolver invocations within a single request. An authenticated user could exploit GraphQL aliasing to repeat an expensive relational query many times in a single request, forcing the server to execute a large number of independent complex database queries concurrently, multiplying database load linearly with the number of aliases. The existing token limit on GraphQL queries still permitted enough aliases for significant resource exhaustion, while the relational depth limit applied per alias without reducing the total number executed. Rate limiting is disabled by default, meaning no built-in throttle prevented this from causing CPU, memory, and I/O exhaustion that could degrade or crash the service. Any authenticated user, including those with minimal read-only permissions, could trigger this condition.
Fix
A request-scoped resolver deduplication mechanism was introduced and applied broadly across all GraphQL read resolvers, both system and items endpoints. When multiple aliases in a single request invoke the same resolver with identical arguments, only the first call executes; all subsequent aliases share its result. This eliminates the amplification factor regardless of how many aliases a query contains.
Impact
- Service degradation or outage: Concurrent complex database queries exhaust the connection pool and server resources, affecting all users
- Low privilege required: Any authenticated user, including those with read-only access to a single collection, can trigger this condition
- Linear scaling: Impact scales with the number of aliases and depth of relational queries
- Compounded by concurrency: Multiple simultaneous requests multiply the effect further
Credited to liyander.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-129239
Directus: Share update allows reassigning user_created and role
medium6.5Nov 16, 2026CVE-2026-61835
Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
high7.7Jul 20, 2026CVE-2026-61836
Directus: Authorization-dependent response served from unsegmented cache key
high8.6Jul 20, 2026CVE-2026-35408
Directus: Missing Cross-Origin Opener Policy
high8.7Apr 4, 2026CVE-2026-35409
Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
high7.7Apr 4, 2026CVE-2026-35410
Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
medium6.1Apr 4, 2026
