Vulnerability Database · npm · Package report

@payloadcms/db-sqlite: vulnerability history, versions and safety

@payloadcms/db-sqlite is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 6 releases, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on @payloadcms/db-sqlite 3.92.0 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.92.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 07 Oct 2026 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Stars 45,357 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT 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 @payloadcms/db-sqlite, 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
4.0.0-internal.970009e 22 Oct 2026 none MIT — Details →
3.92.0 22 Oct 2026 none MIT — Details →
4.0.0-beta.4 22 Oct 2026 none MIT — Details →
4.0.0-internal.0731f09 22 Oct 2026 none MIT — Details →
4.0.0-internal.d7d662c 21 Oct 2026 none MIT — Details →
4.0.0-internal.d3909a9 20 Oct 2026 none MIT — Details →
4.0.0-beta.3 19 Oct 2026 none MIT — Details →
4.0.0-internal.f2a04f7 16 Oct 2026 none MIT — Details →
4.0.0-internal.4a6b4c3 16 Oct 2026 none MIT — Details →
4.0.0-internal.7d5c665 16 Oct 2026 none MIT — Details →
4.0.0-internal.c6494b5 16 Oct 2026 none MIT — Details →
4.0.0-internal.bf4bcce 16 Oct 2026 none MIT — Details →
4.0.0-beta.2 16 Oct 2026 none MIT — Details →
3.91.0 15 Oct 2026 none MIT — Details →
4.0.0-internal.2a3c3bc 14 Oct 2026 none MIT — Details →
4.0.0-internal.8089ef7 14 Oct 2026 none MIT — Details →
4.0.0-beta.1 13 Oct 2026 none MIT — Details →
4.0.0-internal.3b50481 09 Oct 2026 none MIT — Details →
4.0.0-beta.0 09 Oct 2026 none MIT — Details →
4.0.0-internal.4c2ee12 08 Oct 2026 none MIT — Details →
4.0.0-canary.39 08 Oct 2026 none MIT — Details →
4.0.0-internal.ea6e8f8 08 Oct 2026 none MIT — Details →
4.0.0-internal.934870d 08 Oct 2026 none MIT — Details →
4.0.0-canary.38 07 Oct 2026 none MIT — Details →
4.0.0-internal.5e065b3 07 Oct 2026 none MIT — Details →
4.0.0-internal.f15737c 07 Oct 2026 none MIT — Details →
4.0.0-internal.ce66a41 07 Oct 2026 none MIT — Details →
4.0.0-internal.58473b9 06 Oct 2026 none MIT — Details →
4.0.0-internal.21320b5 06 Oct 2026 none MIT — Details →
4.0.0-internal.8001944 06 Oct 2026 none MIT — Details →
4.0.0-internal.442e8b6 05 Oct 2026 none MIT — Details →
3.91.0-internal.07e4582 05 Oct 2026 none MIT — Details →
4.0.0-internal.cd47d20 01 Oct 2026 none MIT — Details →
4.0.0-internal.31ba7ee 01 Oct 2026 none MIT — Details →
4.0.0-internal.cb69780 30 Sep 2026 none MIT — Details →
4.0.0-internal.44ac9c8 29 Sep 2026 none MIT — Details →
4.0.0-internal.d21c039 28 Sep 2026 none MIT — Details →
4.0.0-internal.b8a92d2 28 Sep 2026 none MIT — Details →
3.91.0-internal.c1569dc 25 Sep 2026 none MIT — Details →
4.0.0-internal.77191e5 25 Sep 2026 none MIT — Details →
4.0.0-canary.37 24 Sep 2026 none MIT — Details →
3.90.2 23 Sep 2026 none MIT — Details →
4.0.0-canary.36 21 Sep 2026 none MIT — Details →
3.91.0-internal.6e3dc85 21 Sep 2026 none MIT — Details →
4.0.0-canary.35 18 Sep 2026 none MIT — Details →
3.90.1 18 Sep 2026 none MIT — Details →
4.0.0-canary.34 18 Sep 2026 none MIT — Details →
3.90.0 18 Sep 2026 none MIT — Details →
4.0.0-internal.b8e7c89 14 Sep 2026 none MIT — Details →
3.89.0 10 Sep 2026 H1 MIT Yes Details →
4.0.0-canary.33 08 Sep 2026 none MIT — Details →
4.0.0-internal.3ed7230 08 Sep 2026 none MIT — Details →
4.0.0-canary.32 08 Sep 2026 none MIT — Details →
4.0.0-internal.fec2230 08 Sep 2026 none MIT — Details →
3.89.0-internal.95c9cba 07 Sep 2026 H1 MIT Yes Details →
4.0.0-canary.31 02 Sep 2026 none MIT — Details →
4.0.0-internal.aa277b8 01 Sep 2026 none MIT — Details →
3.89.0-internal.4b0e9b6 01 Sep 2026 H1 MIT Yes Details →
4.0.0-internal.5a4aa81 01 Sep 2026 none MIT — Details →
4.0.0-internal.4e1f822 01 Sep 2026 none MIT — Details →
4.0.0-canary.30 31 Aug 2026 none MIT — Details →
4.0.0-internal.a1317b2 31 Aug 2026 none MIT — Details →
4.0.0-internal.9496957 31 Aug 2026 none MIT — Details →
4.0.0-internal.cc18726 28 Aug 2026 none MIT — Details →
4.0.0-internal.016994f 25 Aug 2026 none MIT — Details →
4.0.0-canary.29 21 Aug 2026 none MIT — Details →
4.0.0-internal.af6aad0 20 Aug 2026 none MIT — Details →
4.0.0-internal.314c594 19 Aug 2026 none MIT — Details →
4.0.0-internal.2f0d313 18 Aug 2026 none MIT — Details →
4.0.0-internal.f715c6e 17 Aug 2026 none MIT — Details →
4.0.0-canary.28 14 Aug 2026 none MIT — Details →
4.0.0-internal.567a487 14 Aug 2026 none MIT — Details →
4.0.0-internal.f05c47f 13 Aug 2026 none MIT — Details →
3.88.0 11 Aug 2026 H1 MIT Yes Details →
4.0.0-canary.27 11 Aug 2026 none MIT — Details →
4.0.0-internal.e38d3ac 11 Aug 2026 none MIT — Details →
4.0.0-canary.26 07 Aug 2026 none MIT — Details →
4.0.0-canary.25 07 Aug 2026 none MIT — Details →
4.0.0-internal.f11981a 07 Aug 2026 none MIT — Details →
3.87.1 06 Aug 2026 H1 MIT Yes Details →
4.0.0-canary.24 06 Aug 2026 none MIT — Details →
4.0.0-canary.23 05 Aug 2026 none MIT — Details →
4.0.0-internal.a7ca468 05 Aug 2026 none MIT — Details →
4.0.0-canary.22 04 Aug 2026 none MIT — Details →
4.0.0-canary.21 04 Aug 2026 none MIT — Details →
4.0.0-internal.7e57eed 03 Aug 2026 none MIT — Details →
4.0.0-internal.8709764 03 Aug 2026 none MIT — Details →
4.0.0-internal.532221d 03 Aug 2026 none MIT — Details →
4.0.0-internal.dee5eab 03 Aug 2026 none MIT — Details →
3.87.0 31 Jul 2026 H1 MIT Yes Details →
4.0.0-canary.20 31 Jul 2026 none MIT — Details →
4.0.0-internal.d1cc1d3 31 Jul 2026 none MIT — Details →
4.0.0-internal.4a8e202 30 Jul 2026 none MIT — Details →
4.0.0-internal.b6f3b9a 30 Jul 2026 none MIT — Details →
4.0.0-internal.167c7cd 30 Jul 2026 none MIT — Details →
4.0.0-internal.164164a 30 Jul 2026 none MIT — Details →
4.0.0-internal.c3ac604 30 Jul 2026 none MIT — Details →
4.0.0-canary.19 29 Jul 2026 none MIT — Details →
4.0.0-canary.18 28 Jul 2026 none MIT — Details →
4.0.0-internal.a6582c6 28 Jul 2026 none MIT — Details →
4.0.0-canary.17 28 Jul 2026 none — — Details →
4.0.0-internal.0b9bec1 23 Jul 2026 none — — Details →
4.0.0-canary.16 22 Jul 2026 none — — Details →
4.0.0-canary.15 21 Jul 2026 none — — Details →
4.0.0-internal.e7d4ebc 21 Jul 2026 none — — Details →
4.0.0-canary.14 21 Jul 2026 none — — Details →
4.0.0-internal.add4c47 21 Jul 2026 none — — Details →
4.0.0-internal.ccea85d 17 Jul 2026 none — — Details →
4.0.0-internal.9726517 17 Jul 2026 none — — Details →
4.0.0-internal.7b031c8 16 Jul 2026 none — — Details →
4.0.0-internal.f851106 16 Jul 2026 none — — Details →
4.0.0-internal.656159a 16 Jul 2026 none — — Details →
4.0.0-internal.c7d5de4 16 Jul 2026 none — — Details →
4.0.0-internal.5852d1a 16 Jul 2026 none — — Details →
4.0.0-internal.8867dba 16 Jul 2026 none — — Details →
4.0.0-internal.e55ccef 16 Jul 2026 none — — Details →
4.0.0-internal.fa183d3 15 Jul 2026 none — — Details →
4.0.0-internal.078835b 15 Jul 2026 none — — Details →
4.0.0-internal.21664f3 15 Jul 2026 none — — Details →
4.0.0-canary.13 15 Jul 2026 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @payloadcms/db-sqlite

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 @payloadcms/db-sqlite

Is @payloadcms/db-sqlite safe to use?

Vulert records 1 vulnerabilities for @payloadcms/db-sqlite in npm: 0 critical, 1 high, 0 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 @payloadcms/db-sqlite's Vulert package health score?

Vulert scores @payloadcms/db-sqlite 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 @payloadcms/db-sqlite affected?

No. 3.92.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.

How many vulnerabilities does @payloadcms/db-sqlite have?

1 vulnerability is recorded for @payloadcms/db-sqlite in the npm ecosystem: 0 critical, 1 high, 0 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 @payloadcms/db-sqlite vulnerabilities disclosed?

1 vulnerability was recorded for @payloadcms/db-sqlite in the last 12 months, and the oldest entry in this database dates to 07 Oct 2026. 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 @payloadcms/db-sqlite 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 @payloadcms/db-sqlite for upcoming vulnerabilities?

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