Quick answers
- Is CVE-2026-35412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35412 being exploited in the wild.
- How severe is CVE-2026-35412?
- High severity, with a CVSS score of 7.1, published 6 April 2026.
- Which products and versions are affected?
- directus (npm) SEMVER:introduced=0,fixed=11.16.1.
- Is there a fix for CVE-2026-35412?
- Yes. directus (npm): upgrade to 11.16.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35412 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35412?
- Check whether you run directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- directus (npm): upgrade to 11.16.1 or later
npm install directus@11.16.1
Technical details
An incorrect authorization vulnerability (CWE-863) exists in the Directus TUS resumable upload endpoint (/files/tus). While the standard REST upload path correctly enforces item-level permissions, the TUS controller only performs collection-level checks on the 'directus_files' table. This allows an authenticated attacker with basic upload privileges to provide a specific file UUID and overwrite the target file's content and metadata, bypassing row-level security rules (e.g., 'owner-only' restrictions). The vulnerability results in the deletion of the original file from storage and its replacement with attacker-controlled data. This is resolved in version 11.16.1; a temporary workaround is to set TUS_ENABLED=false.
Affected products
- Directus Directus < 11.16.1
Identifiers
- CVE-2026-35412
- GHSA-qqmv-5p3g-px89
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-06: disclosed: CVE published to NVD
- 2026-04-06: patched: Fix released in version 11.16.1