Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
CVE-2026-35410GHSA-cf45-hxwj-4cfj
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (directus 11.16.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm directus
- Affected
- < 11.16.1
- Fixed in
- 11.16.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-cf45-hxwj-4cfj lists affected ranges: npm directus >=0 <11.16.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cf45-hxwj-4cfj lists affected ranges: npm directus >=0 <11.16.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- CVE-2026-35410: 0.26% estimated exploitation activity in the next 30 days; percentile 17.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An open redirect vulnerability exists in the login redirection logic. The isLoginRedirectAllowed function fails to correctly identify certain malformed URLs as external, allowing attackers to bypass redirect allow-list validation and redirect users to arbitrary external domains upon successful authentication. Details A parser differential exists between the server-side URL validation logic and how modern browsers interpret URL path segments containing backslashes. Specifically, certain URL patterns are incorrectly classified as safe relative paths by the server, but are normalized by browsers into external domain references. This is particularly impactful in SSO authentication flows (e.g., OAuth2 providers), where an attacker can craft a login URL that redirects the victim to an attacker-controlled site immediately after successful authentication, without any visible indication during the login process. Impact - Phishing: Users may be silently redirected to…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-cf45-hxwj-4cfj
- Revision 1 · created ·
Published from osv record GHSA-cf45-hxwj-4cfj
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-35410 Advisory: Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow IDs: CVE-2026-35410, GHSA-cf45-hxwj-4cfj Record: https://patchnext.com/advisories/cve-2026-35410 (revision 2, source checked 26 Oct 2026, 12:48 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: directus 11.16.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm directus: affected < 11.16.1; fixed in 11.16.1 ## 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-cf45-hxwj-4cfj (OSV record GHSA-cf45-hxwj-4cfj lists affected ranges: npm directus >=0 <11.16.1 (fixed)) - Verified: https://github.com/advisories/GHSA-cf45-hxwj-4cfj (GitHub-reviewed advisory GHSA-cf45-hxwj-4cfj lists affected ranges: npm directus >=0 <11.16.1) Commands are suggestions: review each one before running it.
Loading voting…