CVE-2025-64746

Directus does not properly clean up field-level permissions when a field is deleted. If a new field with the same name is created later, the system automatically re-applies the old permissions, which can lead to unauthorized access.

Details

When a field is removed from a collection, its reference in the permissions table remains intact. This stale reference creates a security gap: if another field is later created using the same name, it inherits the outdated permission entry.
This behavior can unintentionally grant roles access to data they should not be able to read or modify.

The issue is particularly risky in multi-tenant or production environments, where administrators may reuse field names, assuming old permissions have been fully cleared.

1.	Create a collection named test_collection.
2.	Add a field called secret_field.
3.	Assign a role with read permissions specifically tied to secret_field.
4.	Remove the secret_field from the collection.
5.	Create a new field with the exact same name secret_field.
6.	Notice that the previously assigned permissions are still active, granting access to the newly created field without reconfiguration.

When creating new fields with the same name as previously deleted fields it may inherit the permissions of that previously deleted field. This can potentially result in accidentally giving access to this new field in existing policies.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2025-64746 has a CVSS score of 4.6 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.13.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-64746? CVE-2025-64746 is a medium-severity incorrect authorization vulnerability in directus (npm), affecting versions < 11.13.0. It is fixed in 11.13.0. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2025-64746? CVE-2025-64746 has a CVSS score of 4.6 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of directus are affected by CVE-2025-64746? directus (npm) versions < 11.13.0 is affected.
4. Is there a fix for CVE-2025-64746? Yes. CVE-2025-64746 is fixed in 11.13.0. Upgrade to this version or later.
5. Is CVE-2025-64746 exploitable, and should I be worried? Whether CVE-2025-64746 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-64746 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-64746? Upgrade directus to 11.13.0 or later.