CVE-2025-27089: Directus allows updates to non-allowed fields due to overlapping policies
Summary If there are two overlapping policies for the update action that allow access to different fields, instead of correctly checking access permissions against the item they apply for the user is allowed to update the superset of fields allowed by any of the policies. E.g. have one policy allowing update access to fielda if the id == 1 and one policy allowing update access to fieldb if the id == 2.
Published Feb 19, 2025
Affected packages
directus
- Ecosystem
- npm
- Affected
- >= 11.0.0, < 11.1.2
- Fixed in
- 11.1.2
- Check
npm ls directus
@directus/api
- Ecosystem
- npm
- Affected
- >= 22.0.0, < 23.1.0
- Fixed in
- 23.1.0
- Check
npm ls @directus/api
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
If there are two overlapping policies for the update action that allow access to different fields, instead of correctly checking access permissions against the item they apply for the user is allowed to update the superset of fields allowed by any of the policies.
E.g. have one policy allowing update access to field_a if the id == 1 and one policy allowing update access to field_b if the id == 2. The user with both these policies is allowed to update both field_a and field_b for the items with ids 1 and 2.
Details
Before v11, if a user was allowed to update an item they were allowed to update the fields that the single permission, that applied to that item, listed. With overlapping permissions this isn't as clear cut anymore and the union of fields might not be the fields the user is allowed to update for that specific item.
The solution that this PR introduces is to evaluate the permissions for each field that the user tries to update in the validateItemAccess DB query, instead of only verifying access to the item as a whole. This is done by, instead of returning the actual field value, returning a flag that indicates if the user has access to that field. This uses the same case/when mechanism that is used for stripping out non permitted field that is at the core of the permissions engine.
As a result, for every item that the access is validated for, the expected result is an item that has either 1 or null for all the "requested" fields instead of any of the actual field values. These results are not useful for anything other than verifying the field level access permissions.
The final check in validateItemAccess can either fail if the number of items does not match the number of items the access is checked for (ie. the user does not have access to the item at all) or if not all of the passed in fields have access permissions for any of the returned items.
Impact
This is a vulnerability that allows update access to unintended fields, potentially impacting the password field for user accounts.
Credited to hanneskuettner.
References
- https://github.com/directus/directus/security/advisories/GHSA-99vm-5v2h-h6r6
- https://github.com/directus/directus/commit/a7ea67783b060d0d6fc964d71c2d4575d5eee4e2
- https://nvd.nist.gov/vuln/detail/CVE-2025-27089
- https://github.com/directus/directus/releases/tag/v11.1.2
- https://github.com/advisories/GHSA-99vm-5v2h-h6r6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-129239
Directus: Share update allows reassigning user_created and role
medium6.5Nov 16, 2026CVE-2026-61835
Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
high7.7Jul 20, 2026CVE-2026-61836
Directus: Authorization-dependent response served from unsegmented cache key
high8.6Jul 20, 2026CVE-2026-35408
Directus: Missing Cross-Origin Opener Policy
high8.7Apr 4, 2026CVE-2026-35409
Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
high7.7Apr 4, 2026CVE-2026-35410
Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
medium6.1Apr 4, 2026
