Quick answers
- Is CVE-2026-35411 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35411 being exploited in the wild.
- How severe is CVE-2026-35411?
- Medium severity, with a CVSS score of 4.3, 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-35411?
- 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-35411 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-35411?
- 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 open redirect vulnerability (CWE-601) exists in Directus prior to version 11.16.1. The flaw is located in the `/admin/tfa-setup` component, which accepts a user-supplied URL in the `redirect` query parameter. When an administrator who has not yet configured Two-Factor Authentication (2FA) completes the setup process via a crafted link, the application redirects them to the specified external URL without validation. This requires user interaction (completing 2FA setup) but no prior authentication from the attacker. The vulnerability is fixed in version 11.16.1.
Affected products
- Directus Directus < 11.16.1
Identifiers
- CVE-2026-35411
- GHSA-q75c-4gmv-mg9x
Timeline
- 2026-04-02: advisory: GitHub Security Advisory published
- 2026-04-06: disclosed: CVE published to NVD