CVE-2026-22032

Security Advisory: Open Redirect in Directus SAML Authentication

An open redirect vulnerability exists in the Directus SAML authentication callback endpoint. The RelayState parameter is used in redirects without proper validation against an allowlist of permitted domains.

Vulnerability Description

During SAML authentication, the RelayState parameter is intended to preserve the user's original destination. However, while the login initiation flow validates redirect targets against allowed domains, this validation is not applied to the callback endpoint. This allows an attacker to craft a malicious authentication request that redirects users to an arbitrary external URL upon completion.

The vulnerability is present in both the success and error handling paths of the callback.

• Phishing: Users can be redirected to attacker-controlled sites that mimic legitimate login pages
• Credential theft: Chained attacks may leverage the redirect to capture OAuth tokens or authorization codes
• Trust erosion: Users may lose confidence in the application's security posture

This vulnerability can be exploited without authentication.

Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.

CVE-2026-22032 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.14.0, 32.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-22032? CVE-2026-22032 is a medium-severity open redirect vulnerability in directus (npm), affecting versions < 11.14.0. It is fixed in 11.14.0, 32.1.1. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
2. How severe is CVE-2026-22032? CVE-2026-22032 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-22032?
   • directus (npm) (versions < 11.14.0)
   • @directus/api (npm) (versions < 32.1.1)
4. Is there a fix for CVE-2026-22032? Yes. CVE-2026-22032 is fixed in 11.14.0, 32.1.1. Upgrade to this version or later.
5. Is CVE-2026-22032 exploitable, and should I be worried? Whether CVE-2026-22032 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-22032 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-22032?
   • Upgrade directus to 11.14.0 or later
   • Upgrade @directus/api to 32.1.1 or later