Directus: GraphQL Schema SDL Disclosure Setting

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-35413: 0.32% estimated exploitation activity in the next 30 days; percentile 24.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary When GRAPHQLINTROSPECTION=false is configured, Directus correctly blocks standard GraphQL introspection queries (schema, type). However, the serverspecsgraphql 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. Impact Administrators who set GRAPHQLINTROSPECTION=false to hide schema structure from clients would have had a false sense of security, as equivalent schema information remained accessible via the SDL endpoint without authentication. Credit This vulnerability was discovered and reported by bugbunny.ai.

Published by the source

4 Apr 2026, 06:10 UTC

Last modified by the source

7 Apr 2026, 14:35 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wxwm-3fxv-mrvx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wxwm-3fxv-mrvx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35413

Advisory: Directus: GraphQL Schema SDL Disclosure Setting
IDs: CVE-2026-35413, GHSA-wxwm-3fxv-mrvx
Record: https://patchnext.com/advisories/cve-2026-35413 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: directus 11.16.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm directus: affected < 11.16.1; fixed in 11.16.1

## Suggested inspection (read-only)
- `npm ls directus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on directus.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wxwm-3fxv-mrvx (OSV record GHSA-wxwm-3fxv-mrvx lists affected ranges: npm directus >=0 <11.16.1 (fixed))
- Verified: https://github.com/advisories/GHSA-wxwm-3fxv-mrvx (GitHub-reviewed advisory GHSA-wxwm-3fxv-mrvx lists affected ranges: npm directus >=0 <11.16.1)

Commands are suggestions: review each one before running it.