Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.3amended

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

CVE-2024-45596GHSA-cff8-x7jv-4fm8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (directus 11.1.0, 10.13.3; @directus/api 22.2.0, 21.0.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm directus

    Affected
    < 10.13.3>= 11.0.0-rc.1, < 11.1.0
    Fixed in
    11.1.0, 10.13.3

  • npm @directus/api

    Affected
    < 21.0.1>= 22.0.0, < 22.2.0
    Fixed in
    21.0.1, 22.2.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N · score source
EPSS
  • CVE-2024-45596: 0.66% estimated exploitation activity in the next 30 days; percentile 51.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-cff8-x7jv-4fm8

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-cff8-x7jv-4fm8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-45596

Advisory: Session is cached for OpenID and OAuth2 if `redirect` is not used
IDs: CVE-2024-45596, GHSA-cff8-x7jv-4fm8
Record: https://patchnext.com/advisories/cve-2024-45596 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: directus 11.1.0, 10.13.3; @directus/api 22.2.0, 21.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm directus: affected < 10.13.3; >= 11.0.0-rc.1, < 11.1.0; fixed in 11.1.0, 10.13.3
- npm @directus/api: affected < 21.0.1; >= 22.0.0, < 22.2.0; fixed in 21.0.1, 22.2.0

## Suggested inspection (read-only)
- `npm ls directus --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls @directus/api --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on directus, @directus/api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cff8-x7jv-4fm8 (OSV record GHSA-cff8-x7jv-4fm8 lists affected ranges: npm directus >=0 =11.0.0-rc.1 =0 =22.0.0 <22.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-cff8-x7jv-4fm8 (GitHub-reviewed advisory GHSA-cff8-x7jv-4fm8 lists affected ranges: npm directus >=0 =11.0.0-rc.1 =0 =22.0.0 <22.2.0)

Commands are suggestions: review each one before running it.

Loading voting…