Is CVE-2026-22032 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-22032 being exploited in the wild.

How severe is CVE-2026-22032?

Low severity, with a CVSS score of 3.1, published 6 January 2026.

Which products and versions are affected?

@directus/api (npm) SEMVER:introduced=0,fixed=32.1.1; directus (npm) SEMVER:introduced=0,fixed=11.14.0.

Is there a fix for CVE-2026-22032?

Yes. @directus/api (npm): upgrade to 32.1.1 or later; directus (npm): upgrade to 11.14.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-22032 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-22032?

Check whether you run @directus/api (npm) or directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-22032: Directus open redirect in SAML authentication

CVE-2026-22032 · Severity: low · CVSS 3.1 · Published 2026-01-06

Directus is a flexible backend platform that provides CMS and API capabilities with SAML-based single sign-on support. An open redirect vulnerability in the SAML authentication callback allows attackers to redirect users to arbitrary external websites without authentication. This can be exploited for phishing attacks to steal credentials or OAuth tokens, undermining user trust in the application's security.

Technologies: @directus/api (npm), directus (npm). Vendors: npm.

Quick answers

Is CVE-2026-22032 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-22032 being exploited in the wild.
How severe is CVE-2026-22032?: Low severity, with a CVSS score of 3.1, published 6 January 2026.
Which products and versions are affected?: @directus/api (npm) SEMVER:introduced=0,fixed=32.1.1; directus (npm) SEMVER:introduced=0,fixed=11.14.0.
Is there a fix for CVE-2026-22032?: Yes. @directus/api (npm): upgrade to 32.1.1 or later; directus (npm): upgrade to 11.14.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-22032 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-22032?: Check whether you run @directus/api (npm) or directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@directus/api (npm): upgrade to 32.1.1 or later
```
npm install @directus/api@32.1.1
```
directus (npm): upgrade to 11.14.0 or later
```
npm install directus@11.14.0
```

Technical details

The vulnerability is a CWE-601 URL redirect to untrusted site in Directus's SAML authentication flow. The root cause is insufficient validation of the RelayState parameter in the authentication callback endpoint; while the login initiation flow validates redirect targets against allowed domains, this validation is missing from the callback handler. The attack requires user interaction (users must complete a SAML authentication flow) but no privileges, and is reachable over the network. An attacker can craft a malicious SAML authentication request that, upon completion, redirects users to attacker-controlled sites to perform phishing or credential theft. The vulnerability was patched in Directus 11.14.0 (npm package) and @directus/api 32.1.1; the fix involves validation of the relay state redirect target against an allowlist.

Affected products

Directus directus < 11.14.0
Directus @directus/api < 32.1.1

Identifiers

CVE-2026-22032
GHSA-3573-4c68-g8cc

Timeline

2026-01-06: disclosed: Advisory published GHSA-3573-4c68-g8cc
2026-01-06: patched: Patch released: directus 11.14.0 and @directus/api 32.1.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.