p PatchFirst

PatchFirst · Latest vulnerabilities

@directus/api vulnerabilities

Vulnerabilities published for @directus/api in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 12

  1. CVE-2026-26185

    Medium · CVSS 5.3EPSS 0.48%Fix available

    Directus Affected by User Enumeration via Password Reset Timing Attack

    Directus is a real-time API and App dashboard for managing SQL database content. Before 11.14.1, a timing-based user enumeration vulnerability exists in the password reset functionality. When an invalid reset_url parameter is provided, the response time differs by approximately 500ms between existing and non-existing users, enabling reliable user enumeration. This vulnerability is fixed in 11.14.1.

    • Update to 32.2.0
    Published Updated
  2. CVE-2026-22032

    Medium · CVSS 4.3EPSS 0.23%Fix available

    Directus has open redirect in SAML

    Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 11.14.0, an open redirect vulnerability exists in the Directus SAML authentication callback endpoint. During SAML authentication, the `RelayState` parameter is intended to preserve the user's original destination. However, while the login initiation flow validates redirect targets against allowed domains, this validation is not applied to the callback endpoint. This allows an attacker to craft a malicious authentication request that redirects users to an arbitrary external URL upon completion. The vulnerability is present in both the success and

    • Update to 32.1.1
    Published Updated
  3. CVE-2025-64749

    Medium · CVSS 4.3EPSS 0.35%Fix available

    Directus Vulnerable to Information Leakage in Existing Collections

    Directus is a real-time API and App dashboard for managing SQL database content. An observable difference in error messaging was found in the Directus REST API in versions of Directus prior to version 11.13.0. The `/items/{collection}` API returns different error messages for two cases: when a user tries to access an existing collection which they are not authorized to access, and when user tries to access a non-existing collection. The two differing error messages leak the existence of collections to users which are not authorized to access these collections. Version 11.13.0 fixes the issue.

    • Update to 32.0.0
    Published Updated
  4. CVE-2025-64748

    Medium · CVSS 6.5EPSS 0.3%Fix available

    Directus's conceal fields are searchable if read permissions enabled

    Directus is a real-time API and App dashboard for managing SQL database content. A vulnerability in versions prior to 11.13.0 allows authenticated users to search concealed/sensitive fields when they have read permissions. While actual values remain masked (`****`), successful matches can be detected through returned records, enabling enumeration attacks on sensitive data. Version 11.13.0 fixes the issue.

    • Update to 32.0.0
    Published Updated
  5. CVE-2025-55746

    Critical · CVSS 9.3EPSS 1.4%Public exploitFix available

    Directus allows unauthenticated file upload and file modification due to lacking input sanitization

    Directus is a real-time API and App dashboard for managing SQL database content. From 10.8.0 to before 11.9.3, a vulnerability exists in the file update mechanism which allows an unauthenticated actor to modify existing files with arbitrary contents (without changes being applied to the files' database-resident metadata) and / or upload new files, with arbitrary content and extensions, which won't show up in the Directus UI. This vulnerability is fixed in 11.9.3.

    • Update to 28.0.2
    Published Updated
  6. CVE-2025-30351

    Low · CVSS 3.5EPSS 0.37%Fix available

    Suspended Directus user can continue to use session token to access API

    Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 10.10.0 and prior to version 11.5.0, a suspended user can use the token generated in session auth mode to access the API despite their status. This happens because there is a check missing in `verifySessionJWT` to verify that a user is actually still active and allowed to access the API. One can extract the session token obtained by, e.g. login in to the app while still active and then, after the user has been suspended continue to use that token until it expires. Version 11.5.0 patches the issue.

    • Update to 24.0.1
    Published Updated
  7. CVE-2025-27089

    Medium · CVSS 5.4EPSS 0.24%Fix available

    Overlapping policies allow update to non-allowed fields in directus

    Directus is a real-time API and App dashboard for managing SQL database content. In affected versions if there are two overlapping policies for the `update` action that allow access to different fields, instead of correctly checking access permissions against the item they apply for the user is allowed to update the superset of fields allowed by any of the policies. E.g. have one policy allowing update access to `field_a` if the `id == 1` and one policy allowing update access to `field_b` if the `id == 2`. The user with both these policies is allowed to update both `field_a` and `field_b` for the items with ids `1` and `2`. Before v11, if a u

    • Update to 23.1.0
    Published Updated
  8. CVE-2024-54151

    High · CVSS 7.5EPSS 0.6%Fix available

    Directus allows unauthenticated access to WebSocket events and operations

    Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 11.0.0 and prior to version 11.3.0, when setting `WEBSOCKETS_GRAPHQL_AUTH` or `WEBSOCKETS_REST_AUTH` to "public", an unauthenticated user is able to do any of the supported operations (CRUD, subscriptions) with full admin privileges. This impacts any Directus instance that has either `WEBSOCKETS_GRAPHQL_AUTH` or `WEBSOCKETS_REST_AUTH` set to `public` allowing unauthenticated users to subscribe for changes on any collection or do REST CRUD operations on user defined collections ignoring permissions. Version 11.3.0 fixes the issue.

    • Update to 23.2.0
    Published Updated
  9. CVE-2024-47822

    Medium · CVSS 4.2EPSS 0.31%Fix available

    Directus inserts access token from query string into logs

    Directus is a real-time API and App dashboard for managing SQL database content. Access tokens from query strings are not redacted and are potentially exposed in system logs which may be persisted. The access token in `req.query` is not redacted when the `LOG_STYLE` is set to `raw`. If these logs are not properly sanitized or protected, an attacker with access to it can potentially gain administrative control, leading to unauthorized data access and manipulation. This impacts systems where the `LOG_STYLE` is set to `raw`. The `access_token` in the query could potentially be a long-lived static token. Users with impacted systems should rotate

    • Update to 21.0.0
    Published Updated
  10. CVE-2024-46990

    Medium · CVSS 5EPSS 0.47%Fix available

    SSRF Loopback IP filter bypass in directus

    Directus is a real-time API and App dashboard for managing SQL database content. When relying on blocking access to localhost using the default `0.0.0.0` filter a user may bypass this block by using other registered loopback devices (like `127.0.0.2` - `127.127.127.127`). This issue has been addressed in release versions 10.13.3 and 11.1.0. Users are advised to upgrade. Users unable to upgrade may block this bypass by manually adding the `127.0.0.0/8` CIDR range which will block access to any `127.X.X.X` ip instead of just `127.0.0.1`.

    • Update to 21.0.0
    • Update to 22.1.1
    Published Updated
  11. CVE-2024-45596

    High · CVSS 7.4EPSS 0.66%Fix available

    Directus's session is cached for OpenID and OAuth2 if `redirect` is not used

    Directus is a real-time API and App dashboard for managing SQL database content. An unauthenticated user can access credentials of last authenticated user via OpenID or OAuth2 where the authentication URL did not include redirect query string. This happens because on that endpoint for both OpenId and Oauth2 Directus is using the respond middleware, which by default will try to cache GET requests that met some conditions. Although, those conditions do not include this scenario, when an unauthenticated request returns user credentials. This vulnerability is fixed in 10.13.3 and 11.1.0.

    • Update to 21.0.1
    • Update to 22.2.0
    Published Updated
  12. CVE-2024-39699

    Medium · CVSS 5EPSS 0.43%Fix available

    Directus has a Blind SSRF On File Import

    Directus is a real-time API and App dashboard for managing SQL database content. There was already a reported SSRF vulnerability via file import. It was fixed by resolving all DNS names and checking if the requested IP is an internal IP address. However it is possible to bypass this security measure and execute a SSRF using redirects. Directus allows redirects when importing file from the URL and does not check the result URL. Thus, it is possible to execute a request to an internal IP, for example to 127.0.0.1. However, it is blind SSRF, because Directus also uses response interception technique to get the information about the connect from

    • Update to 17.1.0
    Published Updated

Check your server

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

Check your server →