How severe is GHSA-q75c-4gmv-mg9x?

GHSA-q75c-4gmv-mg9x has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-q75c-4gmv-mg9x?

GHSA-q75c-4gmv-mg9x affects the following packages: directus (npm). Ecosystems affected: npm.

How do I fix GHSA-q75c-4gmv-mg9x?

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

How do I detect GHSA-q75c-4gmv-mg9x 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-q75c-4gmv-mg9x 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-q75c-4gmv-mg9x?

O3 pinpoints whether GHSA-q75c-4gmv-mg9x 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-q75c-4gmv-mg9x actively exploited in the wild?

No public exploit code has been indexed for GHSA-q75c-4gmv-mg9x 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-q75c-4gmv-mg9x?

GHSA-q75c-4gmv-mg9x is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q75c-4gmv-mg9x published, and has it been updated?

GHSA-q75c-4gmv-mg9x 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

Not in CISA KEV

MEDIUM severity

GHSA-q75c-4gmv-mg9x

MEDIUM

GHSA-q75c-4gmv-mg9x is a medium-severity (CVSS 4.3) Open Redirect vulnerability in directus. O3 Security confirms whether GHSA-q75c-4gmv-mg9x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Directus: Open Redirect in Admin 2FA Setup Page

Also known asCVE-2026-35411

Published

Apr 4, 2026

Updated

Apr 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

Directus is vulnerable to an Open Redirect via the redirect query parameter on the /admin/tfa-setup page. When an administrator who has not yet configured Two-Factor Authentication (2FA) visits a crafted URL, they are presented with the legitimate Directus 2FA setup page. After completing the setup process, the application redirects the user to the attacker-controlled URL specified in the redirect parameter without any validation.

This vulnerability could be used in phishing attacks targeting Directus administrators, as the initial interaction occurs on a trusted domain.

Credits

Discovered by Neo by ProjectDiscovery (https://neo.projectdiscovery.io/)

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-q75c-4gmv-mg9x 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-q75c-4gmv-mg9x 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-q75c-4gmv-mg9x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Directus is vulnerable to an Open Redirect via the redirect query parameter on the `/admin/tfa-setup` page. When an administrator who has not yet configured Two-Factor Authentication (2FA) visits a crafted URL, they are presented with the legitimate Directus 2FA setup page. After completing the setup process, the application redirects the user to the attacker-controlled URL specified in the `redirect` parameter without any validation. This vulnerability could be used in phishing attacks targeting Directus administrators, as the initial interaction occurs on a trusted domain. ###

O3 Security · Impact-Aware SCA

Is GHSA-q75c-4gmv-mg9x in your dependencies?

O3 detects GHSA-q75c-4gmv-mg9x 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