Skip to main content

CVE-2026-35442

HIGH
Information Exposure (CWE-200)
2026-04-04 https://github.com/directus/directus GHSA-38hg-ww64-rrwc
8.1
CVSS 3.1 · Vendor: https://github.com/directus/directus
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege user
  2. Exploit
    Query concealed fields with aggregate functions
  3. Execution
    Bypass masking protection via min/max operators
  4. Impact
    Extract raw API tokens and secrets

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Authenticated user with read access to a Directus collection containing fields marked with conceal type. Attacker executes aggregate functions (min, max) combined with groupBy queries to extract concealed values like API tokens and 2FA secrets from directus_users table.

Impact

This vulnerability presents critical real-world risk despite the CVSS 8.1 score understating true impact. The CVSS vector (AV:N/AC:L/PR:L/UI:N) indicates network-accessible exploitation with low complexity requiring only authenticated low-privilege access, meaning any legitimate user account can extract all authentication secrets. The High confidentiality impact and High integrity impact (account takeover enables unauthorized modification) are accurate, though Availability impact should arguably be rated given that harvested admin credentials enable destructive actions. No EPSS score provided in input data, but the combination of low attack complexity, clear exploitation steps in the advisory, and high-value targets (authentication bypass primitives) suggests elevated exploitation probability once awareness spreads. CISA KEV status is negative, indicating no confirmed active exploitation at time of analysis. The SSVC decision framework would rate this as high priority: exploitation status is publicly documented with detailed technique description (though no POC code), the attack is fully automatable via API requests, and technical impact is total credential compromise. The primary risk mitigation is that exploitation requires existing authenticated access, but in multi-tenant or large-organization deployments where low-privilege read access is broadly granted, this barrier is minimal. Any Directus instance exposing the directus_users collection to authenticated users faces immediate risk of complete authentication system compromise.

Exploit ScenarioDerived

An attacker with a low-privilege authenticated account (such as a content editor or read-only API consumer) crafts an aggregate query targeting the directus_users collection, using min() or max() functions against the token or tfa_secret fields combined with groupBy clauses to enumerate all values. Because the concealment masking logic fails to process the nested aggregate response structure, the query returns raw database values instead of masked placeholders. The attacker extracts static API tokens for administrator accounts, then authenticates directly to the Directus API with full admin privileges, bypassing password requirements. Alternatively, they harvest TOTP seeds, generate valid time-based codes using standard authenticator algorithms, and defeat two-factor authentication protections during login. No public proof-of-concept code exists at time of analysis, but the attack technique is fully documented in the security advisory with sufficient detail for reproduction.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 04, 2026

Directus CMS aggregate query functions bypass field-level concealment controls, exposing static API tokens and TOTP secrets from the directus_users table to any authenticated user with read access. Attackers can extract credentials for all accounts via min/max operations combined with groupBy clauses, enabling account takeover and two-factor authentication bypass. CVSS 8.1 (High) reflects network-accessible attack requiring only low-privilege authentication. No public exploit code or CISA KEV listing identified at time of analysis, though the attack vector is clearly documented in the GitHub security advisory.

RemediationAI

Apply the vendor-released security patch available through the official GitHub security advisory at https://github.com/directus/directus/security/advisories/GHSA-38hg-ww64-rrwc and https://github.com/advisories/GHSA-38hg-ww64-rrwc. The advisory should specify patched versions for npm package upgrade; administrators should update to the latest stable release that includes the fix for aggregate query payload processing. As an interim workaround until patching is complete, restrict read permissions on the directus_users collection to only highly privileged administrator roles, preventing low-privilege accounts from executing any queries (including aggregates) against authentication credential tables. Review access control policies to ensure concealed fields are protected by role-based permissions in addition to field-level masking, implementing defense-in-depth. Audit application logs for unexpected aggregate queries against directus_users or other collections with concealed fields to identify potential exploitation attempts. After patching, rotate all static API tokens and regenerate TOTP secrets for affected user accounts to invalidate any credentials potentially harvested during the vulnerability window.

Affected Packages

npm directus fix: 11.17.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Directus is an open-source headless CMS (pkg:npm/directus) that implements field-level security through a 'conceal' special type, designed to mask sensitive values like API tokens and TOTP seeds during read operations. The vulnerability stems from an architectural inconsistency in how aggregate query results are processed. Standard item queries return flat key-value pairs that the masking logic correctly intercepts, but aggregate functions (min, max) nest results under function names as structured objects. The payload processing layer fails to recursively traverse this nested structure, causing it to skip concealment enforcement entirely. This represents a classic CWE-200 Information Exposure issue where security controls are inconsistently applied across different code paths accessing the same sensitive data. The directus_users collection stores authentication credentials including static API tokens (long-lived bearer tokens for service accounts) and TOTP seeds (base32-encoded secrets for time-based one-time passwords), making it the highest-value target for this attack technique.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (https://github.com/directus/directus) PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Primary rating from Vendor (https://github.com/directus/directus) · only source for this CVE.

CVSS VectorVendor: https://github.com/directus/directus

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch released
Apr 04, 2026 - 08:30 nvd
Patch available
CVE Published
Apr 04, 2026 - 06:13 nvd
HIGH 8.1

DescriptionCVE.org

Summary

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.

Details

Fields marked with conceal are protected by payload processing logic that replaces real values with a masked placeholder on read. This protection works correctly for standard item queries, but aggregate query results are structured differently, operations are nested under their function name rather than appearing as flat field keys. The masking logic does not account for this nested structure, causing it to silently skip concealed fields in aggregate responses and return their raw values to the client.

Impact

  • Account Takeover An authenticated attacker can harvest static API tokens for all users, including administrators, enabling immediate authentication as any account without credentials.
  • 2FA Bypass TOTP seeds stored in directus_users can similarly be extracted, allowing an attacker to bypass two-factor authentication for any account.

Blast Radius

ecosystem impact
† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth
  • 3 npm packages depend on directus (1 direct, 2 indirect)

Ecosystem-wide dependent count for version 11.17.0.

Executive ViewAI

Why It Matters

Directus CMS contains a critical authentication bypass vulnerability (CVE-2026-35442) that allows any authenticated user to extract static API tokens and TOTP secrets from all user accounts via aggregate query functions, directly enabling account takeover and two-factor authentication circumvention. Organizations running affected Directus instances face immediate risk of lateral privilege escalation and complete authentication system compromise, potentially affecting every user account in the system.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable or restrict aggregate query functions at the application or database level; (2) Implement database-level row-level security to prevent authenticated users from querying the directus_users table directly; (3) Enforce API rate limiting and request logging on aggregate endpoints; (4) Restrict API token access to service accounts only, eliminating interactive user tokens; (5) Require VPN or IP allowlisting for all API access; (6) Implement real-time alerting on TOTP secret or token field access attempts.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Threat Intel
1
1 source
Data Quality
5 sources
Confidence: Medium
NVD CVE.org EPSS Vulnrichment GHSA GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

pkg:npm/directus

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy