Advisory

GHSA-cph6-524f-3hgr

Also known as: CVE-2025-64749

Summary

Directus Vulnerable to Information Leakage in Existing Collections

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-11-13 23:07 UTC
Modified
2025-11-15 03:15 UTC

Affected packages and fixes

directus

npm · All systems

Affected

  • introduced 0, fixed 11.13.0 (semver)

Fixed versions

11.13.0

Fix

@directus/api

npm · All systems

Affected

  • introduced 0, fixed 32.0.0 (semver)

Fixed versions

32.0.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences