CVE-2025-64749: Directus Vulnerable to Information Leakage in Existing Collections

Published Nov 13, 2025
·
Updated

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

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
Directus Directus<11.13.0
npm/@directus/api<32.0.0
32.0.0
npm/directus<11.13.0
11.13.0
Monospace Directus Node.js<11.13.0

Event History

Nov 13, 2025
CVE Published
via MITRE·09:34 PM
Data Sourced
via MITRE·09:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
RemedyAffected Software
Advisory Published
via GitHub·11:07 PM
Data Sourced
via GitHub·11:07 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-64749?

The severity of CVE-2025-64749 is considered medium due to potential information disclosure vulnerabilities present in the Directus REST API.

2

How do I fix CVE-2025-64749?

To address CVE-2025-64749, update your Directus installation to version 11.13.0 or later.

3

What versions of Directus are affected by CVE-2025-64749?

CVE-2025-64749 affects all versions of Directus prior to version 11.13.0.

4

What type of vulnerability is CVE-2025-64749?

CVE-2025-64749 is an information disclosure vulnerability related to error messages in the Directus REST API.

5

Can CVE-2025-64749 be exploited by attackers?

Yes, attackers can exploit CVE-2025-64749 to gain insights into the structure of the database through misleading error responses.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203