dbcve.org
DirectusApplication · Monospace

CVE-2026-35413

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 11.16.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.16.1, when GRAPHQL_INTROSPECTION=false is configured, Directus correctly blocks standard GraphQL introspection queries (__schema, __type). However, the server_specs_graphql resolver on the /graphql/system endpoint returns an equivalent SDL representation of the schema and was not subject to the same restriction. This allowed the introspection control to be bypassed, exposing schema structure (collection names, field names, types, and relationships) to unauthenticated users at the public permission level, and to authenticated users at their permitted permission level. This vulnerability is fixed in 11.16.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

When GRAPHQL_INTROSPECTION=false is set, Directus blocks standard GraphQL introspection queries but the server_specs_graphql resolver on /graphql/system returns an SDL representation of the schema without the same restriction, allowing attackers to bypass the introspection control and discover collection names, field names, types, and relationships.

MitigationUpgrade Directus to version 11.16.1 or later which applies the same introspection restrictions to the SDL endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DirectusApplication
Affected:< 11.16.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Directus version
    Check the installed Directus version by reviewing package.json, a .directus-version file, or the /api/health endpoint response. Compare against the affected range: < 11.16.1
    Affected if The installed version is before 11.16.1
  2. Locate GRAPHQL_INTROSPECTION configuration
    Search for the GRAPHQL_INTROSPECTION setting in environment variables (.env file) or the Directus configuration. Look for GRAPHQL_INTROSPECTION=false
    Affected if GRAPHQL_INTROSPECTION is explicitly set to false but the system may still be vulnerable
  3. Test /graphql/system endpoint accessibility
    Send a GET request to the /graphql/system endpoint without authentication or with valid credentials. Observe if the response returns an SDL representation containing collection names, field names, types, or relationships
    Affected if The endpoint returns schema information (SDL) without requiring introspection queries
  4. Verify SDL bypasses introspection restriction
    With GRAPHQL_INTROSPECTION=false configured, query /graphql/system and confirm it still returns schema details that standard __schema or __type introspection queries would block
    Affected if The /graphql/system endpoint returns complete schema SDL while standard introspection is disabled

You are affected if running Directus < 11.16.1 with GRAPHQL_INTROSPECTION=false configured, and the /graphql/system endpoint returns schema SDL that should have been blocked by that setting.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.16.1 or later
Fixed in 11.16.1
Interim mitigation

Upgrade Directus to version 11.16.1 or later which applies the same introspection restrictions to the SDL endpoint.

Recommended fix High confidence

Directus 11.16.1 or later

  1. Upgrade Directus to version 11.16.1 or later by updating your installation
  2. Verify the GRAPHQL_INTROSPECTION configuration setting is properly set according to your security requirements
  3. Test that GraphQL introspection is properly blocked on both /graphql and /graphql/system endpoints after the upgrade
  4. Confirm that schema structure (collection names, field names, types, relationships) is no longer exposed through the /graphql/system endpoint when introspection is disabled

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Directus Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,370
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35413 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data