CVE-2026-22032 is a medium-severity (CVSS 4.3) Open Redirect vulnerability in directus. A fix is available for directus — see the affected versions and patch details below.
Directus has open redirect in SAML
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22032.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
directusnpm@directus/apinpmDescription
Security Advisory: Open Redirect in Directus SAML Authentication
Summary
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.
Impact
- 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | directus | all versions | 11.14.0npm install directus@11.14.0 |
| 📦npm | @directus/api | all versions | 32.1.1npm install @directus/api@32.1.1 |
Affected Products
directusmonospaceDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for directus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update directus to 11.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22032 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is CVE-2026-22032 in your dependencies?
Find it across npm, including transitive dependencies.