Medium

Directus Lacks Session Tokens Invalidation

  • Disclosed: 13.05.2024
  • Updated: 11.10.2026 10:22

Summary

Currently session tokens function like the other JWT tokens where they are not actually invalidated when logging out. The directus_session gets destroyed and the cookie gets deleted but if you captured the cookie value it will still work for the entire expiry time which is set to 1 day by default. Making it effectively a long lived unrevokable stateless token instead of the stateful session token it was meant to be. When authenticating a session token JWT, Directus should also check whether the associated directus_session both still exists and has not expired (although the token should expire at the same time or before the session) to ensure leaked tokens are not valid indefinitely.

Steps to reproduce

  • Copy the current session token from the cookie
  • Refresh and or log out
  • Use the saved session token to check if it is still valid

Impact

The lack of proper session expiration may improve the likely success of certain attacks. For example, a user might access a web site from a shared computer (such as at a library, Internet cafe, or open work environment). Incorrect token invalidation could allow an attacker to use the browser's history to access a Directus instance session previously accessed by the victim.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package directus >= 10.10.0, < 10.11.0 10.11.0

References

CVSS score 5.4/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
Weakness (CWE)
CWE-613
Platform
npm
Package
directus
Disclosed
13.05.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-g65h-35f3-x2w3 - CC BY 4.0

Vulnerability history: directus

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (58) in the archive
Total entries
58
First → latest
04.2022 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 19
  • Medium 34
  • Low 3

Disclosures per year

  1. 2022: 4
  2. 2023: 8
  3. 2024: 14
  4. 2025: 17
  5. 2026: 15
Severity:
  1. High · 7.7 CVE-2026-61835 < 12.0.0 12.0.0
  2. High · 8.7 CVE-2026-35408 < 11.17.0 11.17.0
  3. High · 8.6 CVE-2025-30353 >= 9.12.0, < 11.5.0 11.5.0
  4. High · 7.5 CVE-2024-54151 >= 11.0.0, < 11.3.0 11.3.0
  5. High · 7.4 CVE-2024-45596 < 10.13.3, >= 11.0.0-rc.1, < 11.1.0 10.13.3, 11.1.0
  6. High · 7.5 CVE-2024-39896 >= 9.11, < 10.13.0 10.13.0
  7. High · 6.3 CVE-2024-39701 >= 9.23.0, < 10.6.0 10.6.0
  8. Directus Lacks Session Tokens Invalidation this entry
    Medium · 5.4 CVE-2024-34709 >= 10.10.0, < 10.11.0 10.11.0
  9. High · 8.2 CVE-2024-27295 < 10.8.3 10.8.3
  10. High · 7.5 CVE-2023-45820 >= 10.4.0, < 10.6.2 10.6.2
  11. High · 7.6 ghsa-22rr-f3p8-5gf8 < 10.6.0 10.6.0
  12. Critical · 9.8 CVE-2022-26969 < 9.7.0 9.7.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.