Quick answers
- Is CVE-2026-35410 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35410 being exploited in the wild.
- How severe is CVE-2026-35410?
- Medium severity, with a CVSS score of 6.1, published 6 April 2026.
- Which products and versions are affected?
- directus (npm) < 11.16.1, SEMVER:introduced=0,fixed=11.16.1.
- Is there a fix for CVE-2026-35410?
- 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-35410 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-35410?
- 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 exists in Directus due to a parser differential in the 'isLoginRedirectAllowed' function. The server-side validation logic fails to correctly identify malformed URLs containing backslashes as external, while modern browsers normalize these same patterns into external domain references. This allows an unauthenticated attacker to craft a URL that bypasses the redirect allow-list. The flaw is particularly impactful in OAuth2 and SAML SSO flows, where a user can be silently redirected to an attacker-controlled domain immediately after successful authentication. This can be leveraged for phishing or to capture authorization codes and tokens. The issue is resolved in version 11.16.1.
Affected products
- Directus Directus < 11.16.1
Identifiers
- CVE-2026-35410
- GHSA-cf45-hxwj-4cfj
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