Quick answers
- Is CVE-2026-35413 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35413 being exploited in the wild.
- How severe is CVE-2026-35413?
- Medium severity, with a CVSS score of 5.3, published 6 April 2026.
- Which products and versions are affected?
- directus (npm) SEMVER:introduced=0,fixed=11.16.1.
- Is there a fix for CVE-2026-35413?
- Yes. directus (npm): upgrade to 11.16.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35413 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35413?
- 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.16.1 or later
npm install directus@11.16.1
Technical details
A vulnerability in Directus exists where the 'server_specs_graphql' resolver on the '/graphql/system' endpoint fails to respect the 'GRAPHQL_INTROSPECTION=false' configuration. While standard introspection queries like '__schema' and '__type' are correctly blocked, this specific endpoint returns an equivalent Schema Definition Language (SDL) representation of the entire schema. An unauthenticated attacker can access this endpoint over the network to discover collection names, field names, types, and relationships. This information disclosure bypasses intended security controls designed to hide the schema from public or unauthorized users. The issue is resolved in version 11.16.1.
Affected products
- Directus Directus < 11.16.1
Identifiers
- CVE-2026-35413
- GHSA-wxwm-3fxv-mrvx
Timeline
- 2026-04-02: advisory: Vendor advisory published on GitHub
- 2026-04-06: disclosed: CVE published to NVD
- 2026-04-06: patched: Fix released in version 11.16.1