How severe is GHSA-cf45-hxwj-4cfj?

GHSA-cf45-hxwj-4cfj has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cf45-hxwj-4cfj?

GHSA-cf45-hxwj-4cfj affects the following packages: directus (npm). Ecosystems affected: npm.

How do I fix GHSA-cf45-hxwj-4cfj?

Update directus to 11.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cf45-hxwj-4cfj is resolved across your whole dependency graph.

How do I detect GHSA-cf45-hxwj-4cfj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for directus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-cf45-hxwj-4cfj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cf45-hxwj-4cfj?

O3 pinpoints whether GHSA-cf45-hxwj-4cfj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-cf45-hxwj-4cfj actively exploited in the wild?

No public exploit code has been indexed for GHSA-cf45-hxwj-4cfj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-cf45-hxwj-4cfj?

GHSA-cf45-hxwj-4cfj is classified as CWE-184 (CWE-184), Open Redirect (CWE-601). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cf45-hxwj-4cfj published, and has it been updated?

GHSA-cf45-hxwj-4cfj was published on April 4, 2026 and was last updated on April 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-cf45-hxwj-4cfj

MEDIUM

GHSA-cf45-hxwj-4cfj is a medium-severity (CVSS 6.1) CWE-184 vulnerability in directus. O3 Security confirms whether GHSA-cf45-hxwj-4cfj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow

Also known asCVE-2026-35410

Published

Apr 4, 2026

Updated

Apr 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

directusnpm

22Kdownloads / week

Description

Summary

An open redirect vulnerability exists in the login redirection logic. The isLoginRedirectAllowed function fails to correctly identify certain malformed URLs as external, allowing attackers to bypass redirect allow-list validation and redirect users to arbitrary external domains upon successful authentication.

Details

A parser differential exists between the server-side URL validation logic and how modern browsers interpret URL path segments containing backslashes. Specifically, certain URL patterns are incorrectly classified as safe relative paths by the server, but are normalized by browsers into external domain references.

This is particularly impactful in SSO authentication flows (e.g., OAuth2 providers), where an attacker can craft a login URL that redirects the victim to an attacker-controlled site immediately after successful authentication, without any visible indication during the login process.

Impact

Phishing: Users may be silently redirected to attacker-controlled sites impersonating legitimate services after authenticating.
Credential/token theft: The redirect can be chained to capture OAuth tokens or authorization codes.
Trust erosion: Users lose confidence in the application after being redirected to unexpected domains post-login.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`directus`	all versions	11.16.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for directus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update directus to 11.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cf45-hxwj-4cfj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-cf45-hxwj-4cfj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-cf45-hxwj-4cfj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An open redirect vulnerability exists in the login redirection logic. The `isLoginRedirectAllowed` function fails to correctly identify certain malformed URLs as external, allowing attackers to bypass redirect allow-list validation and redirect users to arbitrary external domains upon successful authentication. ### Details A parser differential exists between the server-side URL validation logic and how modern browsers interpret URL path segments containing backslashes. Specifically, certain URL patterns are incorrectly classified as safe relative paths by the server, but are no

O3 Security · Impact-Aware SCA

Is GHSA-cf45-hxwj-4cfj in your dependencies?

O3 detects GHSA-cf45-hxwj-4cfj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works