VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

directus: vulnerability history, versions and safety

directus is a package in the npm ecosystem. Vulert records 57 vulnerabilities for it across 120 releases, from Apr 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
57 vulnerabilities recorded C2 H19 M33 L3
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
19 in the last 12 months

Most recent disclosure 20 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all directus vulnerabilities

Vulert verdict on directus 12.5.0 i

Updated on 22 Oct 2026

Careful: 12.5.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 57/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 12.5.0 — affected i
  • Vulnerabilities on record 57 over 4 years · 19 in the last year i
  • Latest disclosure 20 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 3 packages i
  • Stars 38,640 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for directus, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
12.5.0 07 Oct 2026 M2 non-standard No Details →
12.4.1 23 Sep 2026 M2 non-standard No Details →
12.4.0 22 Sep 2026 M2 non-standard No Details →
12.3.1 25 Aug 2026 M2 non-standard No Details →
12.3.0 18 Aug 2026 M2 non-standard No Details →
12.2.0 29 Jul 2026 M2 non-standard No Details →
12.1.1 01 Jul 2026 M2 non-standard No Details →
12.1.0 01 Jul 2026 M2 non-standard No Details →
12.0.2 12 Jun 2026 M2 non-standard No Details →
12.0.1 11 Jun 2026 M2 non-standard No Details →
12.0.0 10 Jun 2026 M2 non-standard No Details →
12.0.0-rc.2 05 Jun 2026 H2 M2 non-standard No Details →
12.0.0-rc.1 29 May 2026 H2 M2 non-standard No Details →
11.17.4 30 Apr 2026 H2 M2 BUSL-1.1 No Details →
11.17.3 15 Apr 2026 H2 M2 BUSL-1.1 No Details →
11.17.2 06 Apr 2026 H2 M2 BUSL-1.1 No Details →
11.17.1 30 Mar 2026 H2 M2 BUSL-1.1 No Details →
11.17.0 24 Mar 2026 H2 M2 BUSL-1.1 No Details →
11.16.1 10 Mar 2026 H6 M4 BUSL-1.1 No Details →
11.16.0 04 Mar 2026 H7 M7 BUSL-1.1 No Details →
11.15.4 17 Feb 2026 H8 M7 BUSL-1.1 No Details →
11.15.3 16 Feb 2026 H8 M7 BUSL-1.1 No Details →
11.15.2 12 Feb 2026 H8 M7 BUSL-1.1 No Details →
11.15.1 06 Feb 2026 H8 M7 BUSL-1.1 No Details →
11.15.0 05 Feb 2026 H8 M7 BUSL-1.1 No Details →
11.14.1 14 Jan 2026 H8 M7 BUSL-1.1 No Details →
11.14.0 09 Dec 2025 H8 M8 BUSL-1.1 No Details →
11.13.4 21 Nov 2025 H8 M9 BUSL-1.1 No Details →
11.13.3 19 Nov 2025 H8 M9 BUSL-1.1 No Details →
11.13.2 10 Nov 2025 H8 M9 BUSL-1.1 No Details →
11.13.1 07 Nov 2025 H8 M9 BUSL-1.1 No Details →
11.13.0 04 Nov 2025 H8 M9 BUSL-1.1 No Details →
11.12.0 16 Sep 2025 H8 M13 BUSL-1.1 No Details →
11.11.0 27 Aug 2025 H8 M13 BUSL-1.1 No Details →
11.10.2 12 Aug 2025 H8 M13 BUSL-1.1 No Details →
11.10.1 11 Aug 2025 H8 M13 BUSL-1.1 No Details →
11.10.0 30 Jul 2025 H8 M13 BUSL-1.1 No Details →
11.9.3 09 Jul 2025 H8 M13 BUSL-1.1 No Details →
11.9.2 01 Jul 2025 C1 H8 M13 BUSL-1.1 No Details →
11.9.1 30 Jun 2025 C1 H8 M13 BUSL-1.1 No Details →
11.9.0 25 Jun 2025 C1 H8 M13 BUSL-1.1 No Details →
11.8.0 28 May 2025 C1 H8 M17 BUSL-1.1 No Details →
11.7.2 29 Apr 2025 C1 H8 M17 BUSL-1.1 No Details →
11.7.1 29 Apr 2025 C1 H8 M17 BUSL-1.1 No Details →
11.7.0 29 Apr 2025 C1 H8 M17 BUSL-1.1 No Details →
11.6.1 01 Apr 2025 C1 H8 M17 BUSL-1.1 No Details →
11.6.0 25 Mar 2025 C1 H8 M17 BUSL-1.1 No Details →
11.5.1 28 Feb 2025 C1 H8 M17 BUSL-1.1 No Details →
11.5.0 26 Feb 2025 C1 H8 M17 BUSL-1.1 No Details →
11.4.1 04 Feb 2025 C1 H9 M18 L1 BUSL-1.1 No Details →
11.4.0 16 Jan 2025 C1 H9 M18 L1 BUSL-1.1 No Details →
11.3.5 18 Dec 2024 C1 H9 M18 L1 BUSL-1.1 No Details →
11.3.4 17 Dec 2024 C1 H9 M18 L1 BUSL-1.1 No Details →
11.3.3 16 Dec 2024 C1 H9 M18 L1 BUSL-1.1 No Details →
11.3.2 03 Dec 2024 C1 H9 M18 L2 BUSL-1.1 No Details →
11.3.1 02 Dec 2024 C1 H9 M18 L2 BUSL-1.1 No Details →
10.13.4 02 Dec 2024 C1 H9 M19 L2 BUSL-1.1 No Details →
11.3.0 02 Dec 2024 C1 H9 M18 L2 BUSL-1.1 No Details →
11.2.2 20 Nov 2024 C1 H10 M18 L2 BUSL-1.1 No Details →
11.2.1 06 Nov 2024 C1 H10 M18 L2 BUSL-1.1 No Details →
11.2.0 05 Nov 2024 C1 H10 M18 L2 BUSL-1.1 No Details →
11.1.2 29 Oct 2024 C1 H10 M19 L2 BUSL-1.1 No Details →
11.1.1 08 Oct 2024 C1 H10 M20 L2 BUSL-1.1 No Details →
11.1.0 03 Sep 2024 C1 H10 M20 L2 BUSL-1.1 No Details →
11.0.2 14 Aug 2024 C1 H10 M20 L2 BUSL-1.1 No Details →
11.0.1 08 Aug 2024 C1 H10 M20 L2 BUSL-1.1 No Details →
11.0.0 06 Aug 2024 C1 H10 M20 L2 BUSL-1.1 No Details →
10.13.2 06 Aug 2024 C1 H10 M20 L2 BUSL-1.1 No Details →
11.0.0-rc.3 10 Jul 2024 C1 H9 M19 L2 BUSL-1.1 No Details →
10.13.1 09 Jul 2024 C1 H10 M21 L2 BUSL-1.1 No Details →
10.13.0 02 Jul 2024 C1 H10 M21 L2 BUSL-1.1 No Details →
11.0.0-rc.2 21 Jun 2024 C1 H9 M19 L2 BUSL-1.1 No Details →
11.0.0-rc.1 20 Jun 2024 C1 H9 M19 L2 BUSL-1.1 No Details →
10.12.1 10 Jun 2024 C1 H11 M21 L2 BUSL-1.1 No Details →
10.12.0 04 Jun 2024 C1 H11 M21 L2 BUSL-1.1 No Details →
10.11.2 28 May 2024 C1 H11 M21 L2 BUSL-1.1 No Details →
10.11.1 21 May 2024 C1 H12 M21 L2 BUSL-1.1 No Details →
10.11.0 07 May 2024 C1 H12 M21 L2 BUSL-1.1 No Details →
10.10.7 17 Apr 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.6 17 Apr 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.5 03 Apr 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.4 12 Mar 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.3 11 Mar 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.2 08 Mar 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.1 06 Mar 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.10.0 05 Mar 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.9.3 23 Feb 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.9.2 14 Feb 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.9.1 13 Feb 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.9.0 06 Feb 2024 C1 H12 M23 L2 BUSL-1.1 No Details →
10.8.3 21 Dec 2023 C1 H12 M23 L2 BUSL-1.1 No Details →
10.8.2 22 Nov 2023 C1 H13 M24 L2 BUSL-1.1 No Details →
10.8.1 17 Nov 2023 C1 H13 M24 L2 BUSL-1.1 No Details →
10.8.0 16 Nov 2023 C1 H13 M24 L2 BUSL-1.1 No Details →
10.7.2 02 Nov 2023 H13 M24 L2 BUSL-1.1 No Details →
10.7.1 27 Oct 2023 H13 M24 L2 BUSL-1.1 No Details →
10.7.0 23 Oct 2023 H13 M24 L2 BUSL-1.1 No Details →
10.6.4 20 Oct 2023 H13 M24 L2 BUSL-1.1 No Details →
10.6.3 25 Sep 2023 H13 M24 L2 BUSL-1.1 No Details →
10.6.2 19 Sep 2023 H13 M24 L2 BUSL-1.1 No Details →
10.7.0-beta.0 25 Aug 2023 H13 M24 L2 — No Details →
10.6.1 25 Aug 2023 H14 M24 L2 — No Details →
10.6.0 25 Aug 2023 H14 M24 L2 — No Details →
10.5.3 10 Aug 2023 H16 M24 L2 — No Details →
10.5.2 28 Jul 2023 H16 M24 L2 — No Details →
10.5.1 26 Jul 2023 H16 M24 L2 — No Details →
10.5.0 25 Jul 2023 H16 M24 L2 — No Details →
10.4.3 11 Jul 2023 H16 M25 L2 — No Details →
10.4.2 30 Jun 2023 H16 M25 L2 — No Details →
10.4.1 30 Jun 2023 H16 M25 L2 — No Details →
10.3.1 27 Jun 2023 H15 M25 L2 — No Details →
10.3.0 13 Jun 2023 H15 M25 L2 — No Details →
10.2.1 26 May 2023 H15 M24 L2 — No Details →
10.2.0 26 May 2023 H15 M24 L2 — No Details →
10.1.1 16 May 2023 H15 M24 L2 — No Details →
10.1.0 11 May 2023 H15 M24 L2 — No Details →
10.0.0 26 Apr 2023 H15 M24 L2 — No Details →
9.26.0 24 Apr 2023 H15 M24 L2 — No Details →
9.25.2 20 Apr 2023 H15 M24 L2 — No Details →
9.25.1 13 Apr 2023 H15 M24 L2 — No Details →

The newest 120 of 344 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 8
  • 2024 15
  • 2025 15
  • 2026 15

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 19 of the 57 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for directus

The 5 most severe of 57 vulnerabilities recorded for this package

Search all 57 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-26969: Insecure default value for CORS configuration in directus 9.8 critical 9.7.0 05 Apr 2022
CVE-2025-55746: Directus Unauthenticated File Upload and Modification Vulnerability 9.3 critical 11.9.3 20 Aug 2025
CVE-2022-24814: Cross-site Scripting Vulnerability in directus 8.8 high 9.7.0 05 Apr 2022
CVE-2026-35408: Directus Missing Cross-Origin Opener Policy Vulnerability 8.7 high 11.17.0 04 Apr 2026
CVE-2025-30353: Directus Webhook Trigger Flaw Exposes Sensitive Data 8.6 high 11.5.0 26 Mar 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About directus

Is directus safe to use?

Vulert records 57 vulnerabilities for directus in npm: 2 critical, 19 high, 33 medium and 3 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is directus's Vulert package health score?

Vulert scores directus 57/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of directus affected?

Yes. 12.5.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of directus should I use?

12.5.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does directus have?

57 vulnerabilities are recorded for directus in the npm ecosystem: 2 critical, 19 high, 33 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new directus vulnerabilities disclosed?

19 vulnerabilities were recorded for directus in the last 12 months, and the oldest entry in this database dates to 05 Apr 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of directus are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor directus for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the directus version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.