Directus has Improper Permission Handling on Deleted Fields

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2025-64746: 0.21% estimated exploitation activity in the next 30 days; percentile 10.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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 testcollection. 2. Add a field called secretfield. 3. Assign a role with read permissions specifically tied to secretfield. 4. Remove the secretfield from the collection. 5. Create a new field with the…

Published by the source

14 Nov 2025, 21:45 UTC

Last modified by the source

14 Nov 2025, 21:45 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9x5g-62gj-wqf2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9x5g-62gj-wqf2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64746

Advisory: Directus has Improper Permission Handling on Deleted Fields
IDs: CVE-2025-64746, GHSA-9x5g-62gj-wqf2
Record: https://patchnext.com/advisories/cve-2025-64746 (revision 2, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: directus 11.13.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm directus: affected < 11.13.0; fixed in 11.13.0

## Suggested inspection (read-only)
- `npm ls directus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on directus.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9x5g-62gj-wqf2 (OSV record GHSA-9x5g-62gj-wqf2 lists affected ranges: npm directus >=0 <11.13.0 (fixed))
- Verified: https://github.com/advisories/GHSA-9x5g-62gj-wqf2 (GitHub-reviewed advisory GHSA-9x5g-62gj-wqf2 lists affected ranges: npm directus >=0 <11.13.0)

Commands are suggestions: review each one before running it.