VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@directus/api: vulnerability history, versions and safety

@directus/api is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 51 releases, from Jul 2024 to Apr 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @directus/api vulnerabilities

Vulert verdict on @directus/api 40.0.0 i

Updated on 23 Oct 2026

Good news: 40.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 40.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 40.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 40.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 Apr 2025 i
  • Highest CVSS 5.0 i
  • With no published fix 0 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/api, 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
40.0.0 07 Oct 2026 none non-standard — Details →
39.2.1 23 Sep 2026 none non-standard — Details →
39.2.0 22 Sep 2026 none non-standard — Details →
39.1.0 25 Aug 2026 none non-standard — Details →
39.0.0 18 Aug 2026 none non-standard — Details →
38.0.0 29 Jul 2026 none non-standard — Details →
37.0.1 01 Jul 2026 none non-standard — Details →
37.0.0 01 Jul 2026 none non-standard — Details →
36.0.2 12 Jun 2026 none non-standard — Details →
36.0.1 11 Jun 2026 none non-standard — Details →
36.0.0 10 Jun 2026 none non-standard — Details →
36.0.0-rc.1 05 Jun 2026 none non-standard — Details →
36.0.0-rc.0 29 May 2026 none non-standard — Details →
35.2.0 30 Apr 2026 none BUSL-1.1 — Details →
35.1.0 15 Apr 2026 none BUSL-1.1 — Details →
35.0.2 06 Apr 2026 none BUSL-1.1 — Details →
35.0.1 30 Mar 2026 none BUSL-1.1 — Details →
35.0.0 24 Mar 2026 none BUSL-1.1 — Details →
34.0.1 10 Mar 2026 none BUSL-1.1 — Details →
34.0.0 04 Mar 2026 none BUSL-1.1 — Details →
33.3.1 17 Feb 2026 none BUSL-1.1 — Details →
33.3.0 16 Feb 2026 none BUSL-1.1 — Details →
33.2.0 12 Feb 2026 none BUSL-1.1 — Details →
33.1.1 06 Feb 2026 none BUSL-1.1 — Details →
33.1.0 05 Feb 2026 none BUSL-1.1 — Details →
33.0.0 14 Jan 2026 none BUSL-1.1 — Details →
32.2.0 09 Dec 2025 none BUSL-1.1 — Details →
32.1.1 21 Nov 2025 none BUSL-1.1 — Details →
32.1.0 19 Nov 2025 none BUSL-1.1 — Details →
32.0.2 10 Nov 2025 none BUSL-1.1 — Details →
32.0.1 07 Nov 2025 none BUSL-1.1 — Details →
32.0.0 04 Nov 2025 none BUSL-1.1 — Details →
31.0.0 16 Sep 2025 none BUSL-1.1 — Details →
30.0.0 27 Aug 2025 none BUSL-1.1 — Details →
29.1.1 12 Aug 2025 none BUSL-1.1 — Details →
29.1.0 11 Aug 2025 none BUSL-1.1 — Details →
29.0.0 30 Jul 2025 none BUSL-1.1 — Details →
28.0.3 09 Jul 2025 none BUSL-1.1 — Details →
28.0.2 01 Jul 2025 none BUSL-1.1 — Details →
28.0.1 30 Jun 2025 none BUSL-1.1 — Details →
28.0.0 25 Jun 2025 none BUSL-1.1 — Details →
27.1.0 28 May 2025 none BUSL-1.1 — Details →
27.0.2 29 Apr 2025 none BUSL-1.1 — Details →
27.0.1 29 Apr 2025 none BUSL-1.1 — Details →
27.0.0 29 Apr 2025 none BUSL-1.1 — Details →
26.0.1 01 Apr 2025 none BUSL-1.1 — Details →
26.0.0 25 Mar 2025 none BUSL-1.1 — Details →
25.0.1 28 Feb 2025 none BUSL-1.1 — Details →
25.0.0 26 Feb 2025 none BUSL-1.1 — Details →
24.0.1 04 Feb 2025 none BUSL-1.1 — Details →
24.0.0 16 Jan 2025 none BUSL-1.1 — Details →
23.3.2 18 Dec 2024 none BUSL-1.1 — Details →
23.3.1 17 Dec 2024 none BUSL-1.1 — Details →
23.3.0 16 Dec 2024 none BUSL-1.1 — Details →
23.2.2 03 Dec 2024 none BUSL-1.1 — Details →
23.2.1 02 Dec 2024 none BUSL-1.1 — Details →
21.0.2 02 Dec 2024 none BUSL-1.1 — Details →
23.2.0 02 Dec 2024 none BUSL-1.1 — Details →
23.1.3 20 Nov 2024 none BUSL-1.1 — Details →
23.1.2 06 Nov 2024 none BUSL-1.1 — Details →
23.1.1 05 Nov 2024 none BUSL-1.1 — Details →
23.1.0 29 Oct 2024 none BUSL-1.1 — Details →
23.0.0 08 Oct 2024 none BUSL-1.1 — Details →
21.0.1 03 Sep 2024 none BUSL-1.1 — Details →
22.2.0 03 Sep 2024 none BUSL-1.1 — Details →
22.1.1 14 Aug 2024 none BUSL-1.1 — Details →
22.1.0 08 Aug 2024 none BUSL-1.1 — Details →
22.0.0 06 Aug 2024 none BUSL-1.1 — Details →
21.0.0 06 Aug 2024 none BUSL-1.1 — Details →
21.0.0-rc.0 10 Jul 2024 M1 BUSL-1.1 Yes Details →
20.1.0 09 Jul 2024 M1 BUSL-1.1 Yes Details →
20.0.0 02 Jul 2024 M1 BUSL-1.1 Yes Details →
20.0.0-rc.1 21 Jun 2024 M1 BUSL-1.1 Yes Details →
20.0.0-rc.0 20 Jun 2024 M1 BUSL-1.1 Yes Details →
19.3.1 10 Jun 2024 M1 BUSL-1.1 Yes Details →
19.3.0 04 Jun 2024 M1 BUSL-1.1 Yes Details →
19.2.0 28 May 2024 M1 BUSL-1.1 Yes Details →
19.1.1 21 May 2024 M1 BUSL-1.1 Yes Details →
19.1.0 07 May 2024 M1 BUSL-1.1 Yes Details →
19.0.2 17 Apr 2024 M1 BUSL-1.1 Yes Details →
19.0.1 17 Apr 2024 M1 BUSL-1.1 Yes Details →
19.0.0 03 Apr 2024 M1 BUSL-1.1 Yes Details →
18.2.1 12 Mar 2024 M1 BUSL-1.1 Yes Details →
18.2.0 11 Mar 2024 M1 BUSL-1.1 Yes Details →
18.1.1 08 Mar 2024 M1 BUSL-1.1 Yes Details →
18.1.0 06 Mar 2024 M1 BUSL-1.1 Yes Details →
18.0.0 05 Mar 2024 M1 BUSL-1.1 Yes Details →
17.1.0 23 Feb 2024 M1 BUSL-1.1 Yes Details →
17.0.1 14 Feb 2024 M2 BUSL-1.1 Yes Details →
17.0.0 13 Feb 2024 M2 BUSL-1.1 Yes Details →
16.0.0 06 Feb 2024 M2 BUSL-1.1 Yes Details →
15.0.0 21 Dec 2023 M2 BUSL-1.1 Yes Details →
14.1.2 22 Nov 2023 M2 BUSL-1.1 Yes Details →
14.1.1 17 Nov 2023 M2 BUSL-1.1 Yes Details →
14.1.0 16 Nov 2023 M2 BUSL-1.1 Yes Details →
14.0.2 02 Nov 2023 M2 BUSL-1.1 Yes Details →
14.0.1 27 Oct 2023 M2 BUSL-1.1 Yes Details →
14.0.0 23 Oct 2023 M2 BUSL-1.1 Yes Details →
13.2.0 20 Oct 2023 M2 BUSL-1.1 Yes Details →
13.1.1 25 Sep 2023 M2 BUSL-1.1 Yes Details →
13.1.0 19 Sep 2023 M2 — Yes Details →
13.1.0-beta.0 25 Aug 2023 M2 — Yes Details →
13.0.0 25 Aug 2023 M2 — Yes Details →
12.1.3 10 Aug 2023 M2 — Yes Details →
12.1.2 28 Jul 2023 M2 — Yes Details →
12.1.1 26 Jul 2023 M2 — Yes Details →
12.1.0 25 Jul 2023 M2 — Yes Details →
12.0.3 11 Jul 2023 M2 — Yes Details →
12.0.2 30 Jun 2023 M2 — Yes Details →
12.0.1 30 Jun 2023 M2 — Yes Details →
12.0.0 27 Jun 2023 M2 — Yes Details →
11.1.0 13 Jun 2023 M2 — Yes Details →
11.0.1 26 May 2023 M2 — Yes Details →
11.0.0 26 May 2023 M2 — Yes Details →
10.2.0 16 May 2023 M2 — Yes Details →
10.1.0 11 May 2023 M2 — Yes Details →
10.0.0 26 Apr 2023 M2 — Yes Details →
9.26.0 24 Apr 2023 M2 — Yes Details →
9.25.2 20 Apr 2023 M2 — Yes Details →
9.25.1 13 Apr 2023 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for @directus/api

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Directus Blind SSRF On File Import in @directus/api 5.0 medium 17.1.0 08 Jul 2024
CVE-2024-47822: @directus/api Access Token Exposure in Logs 4.2 medium 21.0.0 14 Apr 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: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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/api

Is @directus/api safe to use?

Vulert records 2 vulnerabilities for @directus/api in npm: 0 critical, 0 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @directus/api's Vulert package health score?

Vulert scores @directus/api 85/100, which reads as healthy. 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).

Is the latest version of @directus/api affected?

No. 40.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @directus/api should I use?

40.0.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/api have?

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

How often are new @directus/api vulnerabilities disclosed?

0 vulnerabilities were recorded for @directus/api in the last 12 months, and the oldest entry in this database dates to 08 Jul 2024. 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/api 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/api for upcoming vulnerabilities?

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