# CVE-2026-22032: Directus has open redirect in SAML

> An attacker can redirect users to arbitrary external URLs via the SAML callback endpoint, potentially facilitating phishing attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jan 2026
- **Updated:** 15 Jan 2026
- **Also known as:** GHSA-3573-4c68-g8cc

## What is CVE-2026-22032?

CVE-2026-22032 is a medium-severity vulnerability in Monospace Directus, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. Prior to version 11.14.0, an open redirect vulnerability exists in the Directus SAML authentication callback endpoint. 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. This vulnerability can be exploited without authentication. Version 11.14.0 contains a patch.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-22032?

4 open source packages ship an affected version, including @directus/api and directus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@directus/api` | npm | All versions | 32.1.1 |
| `@directus/api` | npm | All versions | 32.1.1 |
| `directus` | npm | All versions | 11.14.0 |
| `directus` | npm | All versions | 11.14.0 |

Products: Monospace Directus.

## How do I fix CVE-2026-22032?

Upgrade @directus/api to 32.1.1 or later.

## Is CVE-2026-22032 being exploited?

There is no known exploitation of CVE-2026-22032 in the wild and no public exploit code.

## Other vulnerabilities in Monospace Directus

- [CVE-2022-26969](https://insights.sbomify.com/CVE-2022-26969/): Insecure default value for CORS configuration (critical 9.8)
- [CVE-2025-55746](https://insights.sbomify.com/CVE-2025-55746/): Directus allows unauthenticated file upload and file modification due to lacking input sanitization (critical 9.3)
- [CVE-2026-35408](https://insights.sbomify.com/CVE-2026-35408/): Directus is Missing Cross-Origin Opener Policy (high 8.7)
- [CVE-2026-61836](https://insights.sbomify.com/CVE-2026-61836/): Directus: Authorization-dependent response served from unsegmented cache key (high 8.6)
- [CVE-2025-30353](https://insights.sbomify.com/CVE-2025-30353/): Directus's webhook trigger flows can leak sensitive data (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22032 and fix it if it is affected.

What it is: CVE-2026-22032 is a medium-severity vulnerability in Monospace Directus, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22032 in the wild and no public exploit code.

Affected packages and fixed versions:
- @directus/api (npm): affected all versions; fixed in 32.1.1
- @directus/api (npm): affected all versions; fixed in 32.1.1
- directus (npm): affected all versions; fixed in 11.14.0
- directus (npm): affected all versions; fixed in 11.14.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22032/ (Markdown: https://insights.sbomify.com/CVE-2026-22032/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22032
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22032
- OSV: https://osv.dev/vulnerability/CVE-2026-22032

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22032/
Summaries are generated and may contain mistakes; the official description above is the record.