Loading vulnerability…
CVE-2025-64749 is an information disclosure issue in Directus affecting versions prior to 11.13.0. The vulnerability is in the Directus REST API endpoint /items/{collection}, which returns observably different error messages depending on whether the requested collection exists but the requester is not authorized to access it, or whether the collection does not exist at all. This discrepancy allows an unauthorized user to distinguish between non-existent collections and real collections that are access-restricted, thereby leaking metadata about the application's data model.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
/items/*. As a compensating control, implement an application-layer control such as a reverse proxy or WAF rule to normalize error responses for /items/{collection} so that requests for unauthorized existing collections and non-existent collections produce indistinguishable responses.Patch, then assume compromise.
@directus/api version 32.0.0 or later as a fixed version. Applying the vendor-provided fix removes the distinguishable error behavior in /items/{collection}.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.