CVE-2025-64749: Directus Directus Vulnerable To Information Leakage Vulnerability

MODERATE
Advisory Identifier: GHSA-cph6-524f-3hgr
Share
CVSS 4.3
CWE-203 CWE-209
Published
Advisory Summary

CVE-2025-64749 is a MODERATE (CVSS 4.3) directus vulnerable to information leakage vulnerability (CWE-203: Observable Discrepancy) affecting Directus libraries in the npm ecosystem. The issue involves directus vulnerable to information leakage in existing collections. Remediation is available by upgrading affected packages to version 11.13.0, 32.0.0.

CVE-2025-64749 at a Glance

CVE Identifier CVE-2025-64749
GHSA Identifier GHSA-cph6-524f-3hgr
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-203: Observable Discrepancy
Affected Product Directus
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-64749

To remediate this vulnerability, upgrade all affected Directus dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

directus fixed: 11.13.0 
npm install directus@11.13.0
@directus/api fixed: 32.0.0 
npm install @directus/api@32.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls directus

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-64749, inspect your project dependencies using npm:

npm ls directus

Analyze the terminal output to locate any version of Directus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 11.13.0), your application is affected.

Note: The npm ls directus command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-203: Observable Discrepancy, where the product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor. In Directus, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary: An observable difference in error messaging was found in the Directus REST API. The `/items/{collection}` API returns different error messages for these two cases: 1. A user tries to access an existing collection which they are not authorized to access. 2. A 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. ### Details: The following response returns an error message, when requesting a collection the user is not authorized to access. ``` GET /items/no-access { "errors": [ { "message": "You don't have permission to access collection \"no-access\" or it does not exist. Queried in root.", "extensions": { "reason": "You don't have permission to access collection \"no-access\" or it does not exist. Queried in root.", "code": "FORBIDDEN" } } ] } ``` The following response returns a different error message when requesting a collection which does not exist. ``` GET /items/does-not-exist { "errors": [ { "message": "You don't have permission to access this.", "extensions": { "code": "FORBIDDEN" } } ] } ``` ### Impact: The difference in errors between non-existent collections and collections blocked by permissions leak the existence of a collection to a user which is not authorized to access this object. ### Credit: Sebastian Krause - [Hackmanit GmbH](https://hackmanit.de)

CVE-2025-64749 Affected Directus Versions

2 component(s)
Fixed Versions:
11.13.032.0.0
Product / Package Ecosystem Affected Versions Fixed Version
directus
npm/directus
npm
< 11.13.0
11.13.0
@directus/api
npm/@directus/api
npm
< 32.0.0
32.0.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/directus/directus/security/advisories/GHSA-cph6-524f-3hgr
NVD — CVE-2025-64749 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-64749
Security Fix Commit FIX COMMIT
https://github.com/directus/directus/commit/f99c9b89071f9d136cc9b0d0c182f2d24542bc31
Directus Source Repository REPOSITORY
https://github.com/directus/directus

Frequently Asked Questions

What is CVE-2025-64749?
CVE-2025-64749 is a security vulnerability in Directus involving Directus Vulnerable to Information Leakage in Existing Collections under CWE-203: Observable Discrepancy.
Which Directus versions are affected?
Affected versions include releases prior to 11.13.0, 32.0.0 across affected packages: directus, @directus/api.
What version fixes CVE-2025-64749?
Upgrading to 11.13.0, 32.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is directus affected?
Yes, directus is affected in releases prior to 11.13.0. Upgrade your dependency to 11.13.0 or later.
Is @directus/api affected?
Yes, @directus/api is affected in releases prior to 32.0.0. Upgrade your dependency to 32.0.0 or later.
What is the CVSS score of CVE-2025-64749?
CVE-2025-64749 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2025-64749?
CVE-2025-64749 is classified under CWE-203: Observable Discrepancy (The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.).
How can I check npm dependencies for CVE-2025-64749?
Run the dependency tree command: 'npm ls directus'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cph6-524f-3hgr",
  "modified" : "2025-11-15T03:15:40Z",
  "published" : "2025-11-13T23:07:31Z",
  "aliases" : [ "CVE-2025-64749" ],
  "summary" : "Directus Vulnerable to Information Leakage in Existing Collections",
  "details" : "### Summary:\n\nAn observable difference in error messaging was found in the Directus REST API. The `/items/{collection}` API returns different error messages for these two cases:\n1. A user tries to access an existing collection which they are not authorized to access.\n2. A user tries to access a non-existing collection.\n\nThe two differing error messages leak the existence of collections to users which are not authorized to access these collections.\n\n### Details:\n\nThe following response returns an error message, when requesting a collection the user is not authorized to access.\n\n```\nGET /items/no-access\n{\n  \"errors\": [\n    {\n      \"message\": \"You don't have permission to access collection \\\"no-access\\\" or it does not exist. Queried in root.\",\n      \"extensions\": {\n        \"reason\": \"You don't have permission to access collection \\\"no-access\\\" or it does not exist. Queried in root.\",\n        \"code\": \"FORBIDDEN\"\n      }\n    }\n  ]\n}\n```\n\nThe following response returns a different error message when requesting a collection which does not exist.\n\n```\nGET /items/does-not-exist\n{\n  \"errors\": [\n    {\n      \"message\": \"You don't have permission to access this.\",\n      \"extensions\": {\n        \"code\": \"FORBIDDEN\"\n      }\n    }\n  ]\n}\n```\n\n### Impact:\n\nThe difference in errors between non-existent collections and collections blocked by permissions leak the existence of a collection to a user which is not authorized to access this object.\n\n### Credit:\n\nSebastian Krause - [Hackmanit GmbH](https://hackmanit.de)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "directus"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "11.13.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@directus/api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "32.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/directus/directus/security/advisories/GHSA-cph6-524f-3hgr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64749"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/directus/directus/commit/f99c9b89071f9d136cc9b0d0c182f2d24542bc31"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/directus/directus"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-203", "CWE-209" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-13T23:07:31Z",
    "nvd_published_at" : "2025-11-13T22:15:52Z"
  }
}