dbcve.org
DirectusApplication · Monospace

CVE-2026-35442

HIGH · 8.1 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 11.17.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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.17.0, aggregate functions (min, max) applied to fields with the conceal special type incorrectly return raw database values instead of the masked placeholder. When combined with groupBy, any authenticated user with read access to the affected collection can extract concealed field values, including static API tokens and two-factor authentication secrets from directus_users. This vulnerability is fixed in 11.17.0.

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

In Directus versions prior to 11.17.0, aggregate functions (min, max) applied to fields with the 'conceal' special type return unmasked raw database values instead of the configured placeholder. When used with groupBy, any authenticated user with read access can extract concealed sensitive data including API tokens and 2FA secrets from the directus_users table.

MitigationUpgrade Directus to version 11.17.0 or later to remediate this vulnerability. Additionally, audit user access controls and consider rotating any exposed credentials.

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.17.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check Directus version
    Locate the installed Directus version (typically in package.json, .env file, or admin panel footer). Compare against the affected range: versions prior to 11.17.0
    Affected if Installed version is less than 11.17.0
  2. Identify concealed fields in use
    Review collection schemas for fields with the 'conceal' special type, particularly in sensitive collections like directus_users where API tokens and 2FA secrets may be stored
    Affected if Concealed fields exist in the database schema
  3. Verify aggregate query capability on concealed fields
    Test whether authenticated users with read access can execute min() or max() aggregate functions on concealed fields via API (e.g., POST to /items/{collection} with aggregate: {min: {field}})
    Affected if Aggregate queries on concealed fields return raw values instead of masked placeholders
  4. Confirm groupBy with aggregate is permitted
    Test combining groupBy with aggregate functions on concealed fields via API (e.g., include both groupBy and aggregate parameters in request)
    Affected if groupBy can be combined with min/max aggregates on concealed fields, returning unmasked data

You are affected if running Directus below 11.17.0 AND you have concealed fields that are accessible to authenticated users who can run aggregate+groupBy queries on those fields.

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.17.0 or later
Fixed in 11.17.0
Interim mitigation

Upgrade Directus to version 11.17.0 or later to remediate this vulnerability. Additionally, audit user access controls and consider rotating any exposed credentials.

Recommended fix High confidence

Directus 11.17.0

  1. Backup your Directus installation and database before upgrading
  2. Upgrade Directus to version 11.17.0 or later
  3. After upgrading, verify that aggregate functions (min, max) on concealed fields now return masked placeholder values instead of raw database values
  4. If using groupBy with concealed fields, confirm the vulnerability is no longer exploitable

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

Fix this in Directus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35442 — 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-35442 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