How severe is GHSA-cff8-x7jv-4fm8?

GHSA-cff8-x7jv-4fm8 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-cff8-x7jv-4fm8?

GHSA-cff8-x7jv-4fm8 affects the following packages: directus (npm), directus (npm), @directus/api (npm), @directus/api (npm). Ecosystems affected: npm.

How do I fix GHSA-cff8-x7jv-4fm8?

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

How do I detect GHSA-cff8-x7jv-4fm8 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-cff8-x7jv-4fm8 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-cff8-x7jv-4fm8?

O3 pinpoints whether GHSA-cff8-x7jv-4fm8 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-cff8-x7jv-4fm8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cff8-x7jv-4fm8 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 is the EPSS score for GHSA-cff8-x7jv-4fm8?

GHSA-cff8-x7jv-4fm8 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-cff8-x7jv-4fm8?

GHSA-cff8-x7jv-4fm8 is classified as CWE-524 (CWE-524). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cff8-x7jv-4fm8 published, and has it been updated?

GHSA-cff8-x7jv-4fm8 was published on September 10, 2024 and was last updated on November 17, 2025. 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-cff8-x7jv-4fm8

HIGH

Session is cached for OpenID and OAuth2 if `redirect` is not used

Also known asCVE-2024-45596

Published

Sep 10, 2024

Updated

Nov 17, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk45th percentile-0.14%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

directusnpm

25Kdownloads / week

@directus/apinpm

24Kdownloads / week

Description

Summary

Unauthenticated user can access credentials of last authenticated user via OpenID or OAuth2 where the authentication URL did not include redirect query string.

For example:

Project is configured with OpenID or OAuth2
Project is configured with cache enabled
User tries to login via SSO link, but without redirect query string
After successful login, credentials are cached
If an unauthenticated user tries to login via SSO link, it will return the credentials of the other last user

The SSO link is something like https://directus.example.com/auth/login/openid/callback, where openid is the name of the OpenID provider configured in Directus

Details

This happens because on that endpoint for both OpenId and Oauth2 Directus is using the respond middleware, which by default will try to cache GET requests that met some conditions. Although, those conditions do not include this scenario, when an unauthenticated request returns user credentials. For OpenID, this can be seen here: https://github.com/directus/directus/blob/main/api/src/auth/drivers/openid.ts#L453-L459 And for OAuth2 can be seen here https://github.com/directus/directus/blob/main/api/src/auth/drivers/oauth2.ts#L422-L428

PoC

Create a new Directus project
Set CACHE_ENABLED to true
Set CACHE_STORE to redis for reliable results (if using memory with multiple nodes, it may only happen sometimes, due to cache being different for different nodes)
Configure REDIS with redis string or redis host, port, user, etc.
Set AUTH_PROVIDERS to openid
Set PUBLIC_URL to the the main URL of your project . For example, PUBLIC_URL: http://localhost:8055
Configure AUTH_OPENID_CLIENT_ID, AUTH_OPENID_CLIENT_SECRET, AUTH_OPENID_ISSUER_URL with proper OpenID configurations
Be sure that on OpenID external app you have configured Redirect URI to http://localhost:8055/auth/login/openid/callback
Run Directus
Open the SSO link like http://localhost:8055/auth/login/openid/callback
Do the authentication on the OpenID external webpage
Verify that it you got redirected to a page with a JSON including access_token property
Be sure all anonymous mode windows are closed
Open an anonymous window and go to the SSO Link http://localhost:8055/auth/login/openid/callback and see you have the same credentials, even though you don't have any session because you are in anonymous mode

Impact

All projects using OpenID or OAuth 2, that does not include redirect query string on loggin in users.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`directus`	all versions	10.13.3
📦npm	`directus`	≥ 11.0.0-rc.1&&< 11.1.0	11.1.0
📦npm	`@directus/api`	all versions	21.0.1
📦npm	`@directus/api`	≥ 22.0.0&&< 22.2.0	22.2.0

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 10.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cff8-x7jv-4fm8 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-cff8-x7jv-4fm8 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-cff8-x7jv-4fm8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Unauthenticated user can access credentials of last authenticated user via OpenID or OAuth2 where the authentication URL did not include `redirect` query string. For example: - Project is configured with OpenID or OAuth2 - Project is configured with cache enabled - User tries to login via SSO link, but without `redirect` query string - After successful login, credentials are cached - If an unauthenticated user tries to login via SSO link, it will return the credentials of the other last user The SSO link is something like `https://directus.example.com/auth/login/openid/callback`,

O3 Security · Impact-Aware SCA

Is GHSA-cff8-x7jv-4fm8 in your dependencies?

O3 detects GHSA-cff8-x7jv-4fm8 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