CVE-2026-35411 directus CVE debrief

Who should care

Directus administrators who have not yet configured Two-Factor Authentication (2FA) should be aware of this vulnerability and take steps to mitigate it. This includes updating Directus to version 11.16.1 or later and configuring 2FA for all administrators. Additionally, administrators should monitor for suspicious activity on the /admin/tfa-setup page.

Technical summary

The vulnerability allows an attacker to redirect the user to a malicious URL after completing the 2FA setup process. This could be used in phishing attacks targeting Directus administrators, as the initial interaction occurs on a trusted domain. The open redirect occurs via the redirect query parameter on the /admin/tfa-setup page. To exploit this vulnerability, an attacker would need to craft a URL that redirects the user to a malicious site.

Defensive priority

Medium

Recommended defensive actions

• Update Directus to version 11.16.1 or later
• Configure Two-Factor Authentication (2FA) for all administrators
• Monitor for suspicious activity on the /admin/tfa-setup page
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-04-06T22:16:22.243Z and last modified on 2026-07-24T21:10:00.143Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus. To verify, defenders should check the official CVE record and NVD entry for any updates. The open redirect vulnerability in Directus, a real-time API and App dashboard for managing SQL database content, allows an attacker to redirect users to a malicious URL after completing the 2FA setup process.

Official resources