p PatchFirst

PatchFirst · Latest vulnerabilities

directus 11.16.1: known vulnerabilities

Known vulnerabilities affecting directus 11.16.1: 8. Compare the fixes below with your installed release.

Filter vulnerabilities
Clear filters

Vulnerabilities: 8

  1. CVE-2026-61836

    High · CVSS 8.6EPSS 0.47%Fix available

    Directus: Authorization-dependent response served from unsegmented cache key

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.0.0, when response caching is enabled, the cache-key derivation in api/src/utils/get-cache-key.ts includes version, path, query, and accountability.user but omits authorization context such as share, role, roles, admin, app, and policies. Directus share tokens and anonymous requests can both reduce to user null, so different shares or anonymous clients requesting the same URL and query can receive a permission-filtered cached response without permission re-evaluation. This issue is fixed in version 12.0.0.

    • Update to 12.0.0
    Published Updated
  2. CVE-2026-61835

    High · CVSS 7.7EPSS 0.41%Fix available

    Directus: SSRF Protection Bypass via 0.0.0.0 in File Import

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to 12.0.0, the SSRF protection on Directus's file-import-from-URL feature can be bypassed using the address 0.0.0.0 because api/src/request/is-denied-ip.ts treats 0.0.0.0 as a keyword for local interfaces but never blocks the literal address itself. On Linux and macOS, connecting to 0.0.0.0 reaches localhost, so an authenticated user with file-upload rights can make the server fetch internal services through the /files/import endpoint and retrieve the response as a downloadable file. This issue is fixed in version 12.0.0.

    • Update to 12.0.0
    Published Updated
  3. CVE-2026-39943

    Medium · CVSS 6.5EPSS 0.17%Fix available

    Directus exposes sensitive fields in revision history

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.17.0, Directus stores revision records (in directus_revisions) whenever items are created or updated. Due to the revision snapshot code not consistently calling the prepareDelta sanitization pipeline, sensitive fields (including user tokens, two-factor authentication secrets, external auth identifiers, auth data, stored credentials, and AI provider API keys) could be stored in plaintext within revision records. This vulnerability is fixed in 11.17.0.

    • Update to 11.17.0
    Published Updated
  4. CVE-2026-39942

    High · CVSS 8.5EPSS 0.2%Fix available

    Directus has a Path Traversal and Broken Access Control in File Management API

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.17.0, the PATCH /files/{id} endpoint accepts a user-controlled filename_disk parameter. By setting this value to match the storage path of another user's file, an attacker can overwrite that file's content while manipulating metadata fields such as uploaded_by to obscure the tampering. This vulnerability is fixed in 11.17.0.

    • Update to 11.17.0
    Published Updated
  5. CVE-2026-35442

    High · CVSS 8.1EPSS 0.34%Fix available

    Directus: Authenticated Users Can Extract Concealed Fields via Aggregate Queries

    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.

    • Update to 11.17.0
    Published Updated
  6. CVE-2026-35441

    Medium · CVSS 6.5EPSS 0.36%Fix available

    Directus Affected by GraphQL Alias Amplification Denial-of-Service Due to Missing Query Cost/Complexity Limits

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.17.0, Directus' GraphQL endpoints (/graphql and /graphql/system) did not deduplicate resolver invocations within a single request. An authenticated user could exploit GraphQL aliasing to repeat an expensive relational query many times in a single request, forcing the server to execute a large number of independent complex database queries concurrently, multiplying database load linearly with the number of aliases. The existing token limit on GraphQL queries still permitted enough aliases for significant resource exhaustion, while the relational depth

    • Update to 11.17.0
    Published Updated
  7. CVE-2026-35408

    High · CVSS 8.7EPSS 0.17%Fix available

    Directus is Missing Cross-Origin Opener Policy

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.17.0, Directus's Single Sign-On (SSO) login pages lacked a Cross-Origin-Opener-Policy (COOP) HTTP response header. Without this header, a malicious cross-origin window that opens the Directus login page retains the ability to access and manipulate the window object of that page. An attacker can exploit this to intercept and redirect the OAuth authorization flow to an attacker-controlled OAuth client, causing the victim to unknowingly grant access to their authentication provider account (e.g. Google, Discord). This vulnerability is fixed in 11.17.0.

    • Update to 11.17.0
    Published Updated
  8. GHSA-6q22-g298-grjh

    High · CVSS 7.5Fix available

    Directus: Unauthenticated Denial of Service via GraphQL Alias Amplification of Expensive Health Check Resolver

    ## Summary The GraphQL specification permits a single query to repeat the same field multiple times using aliases, with each alias resolved independently by default. Directus did not deduplicate resolver invocations within a single request, meaning each alias triggered a full, independent execution of the underlying resolver. The health check resolver ran all backend checks (database connectivity, cache, storage writes, and SMTP verification) on every invocation. Combined with unauthenticated access to the system GraphQL endpoint, this allowed an attacker to amplify resource consumption significantly from a single HTTP request, exhausting t

    • Update to 11.17.0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →