dbcve.org
DirectusApplication · Monospace

CVE-2026-35410

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 11.16.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.16.1, 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. This vulnerability is fixed in 11.16.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Directus versions prior to 11.16.1 contain an open redirect vulnerability 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 authenticated users to arbitrary external domains.

MitigationUpgrade to Directus version 11.16.1 or later to patch the open redirect vulnerability in the login redirection validation logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DirectusApplication
Affected:< 11.16.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Directus installation and version
    Locate the Directus installation directory. Check package.json for the version field, or query the /server/version API endpoint if the instance is accessible, or check the version file in the installation directory if one exists.
    Affected if The installed version is Directus and is lower than 11.16.1
  2. Verify login redirect functionality exists
    Confirm the Directus instance has authentication enabled and login functionality present. This is typically the default configuration for Directus installations.
    Affected if Directus login functionality is enabled and accessible
  3. Confirm isLoginRedirectAllowed function is present
    Locate the source code file containing the isLoginRedirectAllowed function within the Directus installation. This function handles validation of redirect URLs during the login process.
    Affected if The isLoginRedirectAllowed function exists in the codebase and handles login redirect validation

The environment is affected if Directus is installed with a version lower than 11.16.1 and the login redirect functionality with isLoginRedirectAllowed is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.16.1 or later
Fixed in 11.16.1
Interim mitigation

Upgrade to Directus version 11.16.1 or later to patch the open redirect vulnerability in the login redirection validation logic.

Recommended fix High confidence

11.16.1

  1. 1. Back up the Directus database before performing any upgrade
  2. 2. Back up the Directus installation directory and configuration files
  3. 3. Upgrade Directus to version 11.16.1 using your deployment method (npm install [email protected], Docker, or your package manager)
  4. 4. Verify the isLoginRedirectAllowed function has been updated to properly validate malformed URLs
  5. 5. Test the login redirect functionality to confirm the vulnerability is patched

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Directus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35410 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data