{"answers":{"affected":"4 open source packages ship an affected version, including @directus/api and directus. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64749 in the wild and no public exploit code.","fix":"Upgrade @directus/api to 32.0.0 or later.","what":"CVE-2025-64749 is a medium-severity vulnerability in Monospace Directus, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64749 and fix it if it is affected.\n\nWhat it is: CVE-2025-64749 is a medium-severity vulnerability in Monospace Directus, published on 13 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64749 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @directus/api (npm): affected all versions; fixed in 32.0.0\n- @directus/api (npm): affected all versions; fixed in 32.0.0\n- directus (npm): affected all versions; fixed in 11.13.0\n- directus (npm): affected all versions; fixed in 11.13.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64749/ (Markdown: https://insights.sbomify.com/CVE-2025-64749/index.md)","id":"CVE-2025-64749","markdown":"https://insights.sbomify.com/CVE-2025-64749/index.md","name":"CVE-2025-64749","record":{"aliases":["GHSA-cph6-524f-3hgr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Directus API dashboard","requires_auth":"low_privilege","summary":"Attackers can enumerate existing collections via differing error messages in the Directus REST API, leaking metadata to unauthorized users.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"directus","vendor":"monospace"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"},{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Directus Vulnerable to Information Leakage in Existing Collections","id":"CVE-2025-64749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"monospace:directus","products":["monospace:directus"],"type":"information_disclosure","year":"2025"},"n_packages":4,"n_references":2,"next":{"headline":"Singluarity ineffectively applies of selinux / apparmor LSM process labels","id":"CVE-2025-64750"},"packages":[{"ecosystem":"npm","fixed":["32.0.0"],"introduced":["0"],"last_affected":[],"package":"@directus/api","purl":null,"source":"GHSA-cph6-524f-3hgr"},{"ecosystem":"npm","fixed":["32.0.0"],"introduced":["0"],"last_affected":[],"package":"@directus/api","purl":"pkg:npm/%40directus/api","source":"GHSA-cph6-524f-3hgr"},{"ecosystem":"npm","fixed":["11.13.0"],"introduced":["0"],"last_affected":[],"package":"directus","purl":null,"source":"GHSA-cph6-524f-3hgr"},{"ecosystem":"npm","fixed":["11.13.0"],"introduced":["0"],"last_affected":[],"package":"directus","purl":"pkg:npm/directus","source":"GHSA-cph6-524f-3hgr"}],"prev":{"headline":"Directus's conceal fields are searchable if read permissions enabled","id":"CVE-2025-64748"},"products":["directus"],"published":"2025-11-13","related":[{"cvss_score":9.8,"headline":"Insecure default value for CORS configuration","id":"CVE-2022-26969","kev_date_added":null,"published":"2022-12-26"},{"cvss_score":9.3,"headline":"Directus allows unauthenticated file upload and file modification due to lacking input sanitization","id":"CVE-2025-55746","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":8.7,"headline":"Directus is Missing Cross-Origin Opener Policy","id":"CVE-2026-35408","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.6,"headline":"Directus: Authorization-dependent response served from unsegmented cache key","id":"CVE-2026-61836","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":8.6,"headline":"Directus's webhook trigger flows can leak sensitive data","id":"CVE-2025-30353","kev_date_added":null,"published":"2025-03-26"},{"cvss_score":8.5,"headline":"Directus has a Path Traversal and Broken Access Control in File Management API","id":"CVE-2026-39942","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.2,"headline":"Directus MySQL accent insensitive email matching","id":"CVE-2024-27295","kev_date_added":null,"published":"2024-03-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-14","vendors":["directus"]},"summary":"Attackers can enumerate existing collections via differing error messages in the Directus REST API, leaking metadata to unauthorized users.","url":"https://insights.sbomify.com/CVE-2025-64749/"}