Vulnerability Database · NuGet · Package report

LiteDB: vulnerability history, versions and safety

LiteDB is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 42 releases, first recorded in Feb 2023. 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 C1
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.

Vulert verdict on LiteDB 5.0.21 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 5.0.21 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Feb 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 9,486 i
  • Last release 27 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, 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 LiteDB, 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
6.0.0-prerelease.322 01 Oct 2026 none MIT — Details →
6.0.0-prerelease.321 01 Oct 2026 none MIT — Details →
6.0.0-prerelease.319 28 Sep 2026 none MIT — Details →
6.0.0-prerelease.318 28 Sep 2026 none MIT — Details →
6.0.0-prerelease.317 28 Sep 2026 none MIT — Details →
6.0.0-prerelease.316 28 Sep 2026 none MIT — Details →
6.0.0-prerelease.315 28 Sep 2026 none MIT — Details →
6.0.0-prerelease.311 24 Sep 2026 none MIT — Details →
6.0.0-prerelease.309 24 Sep 2026 none MIT — Details →
6.0.0-prerelease.305 22 Sep 2026 none MIT — Details →
6.0.0-prerelease.304 22 Sep 2026 none MIT — Details →
6.0.0-prerelease.303 22 Sep 2026 none MIT — Details →
6.0.0-prerelease.302 21 Sep 2026 none MIT — Details →
6.0.0-prerelease.300 21 Sep 2026 none MIT — Details →
6.0.0-prerelease.298 21 Sep 2026 none MIT — Details →
6.0.0-prerelease.297 21 Sep 2026 none MIT — Details →
6.0.0-prerelease.296 20 Sep 2026 none MIT — Details →
6.0.0-prerelease.295 20 Sep 2026 none MIT — Details →
6.0.0-prerelease.294 20 Sep 2026 none MIT — Details →
6.0.0-prerelease.292 20 Sep 2026 none MIT — Details →
6.0.0-prerelease.291 20 Sep 2026 none MIT — Details →
6.0.0-prerelease.289 19 Sep 2026 none MIT — Details →
6.0.0-prerelease.275 19 Sep 2026 none MIT — Details →
6.0.0-prerelease.270 18 Sep 2026 none MIT — Details →
6.0.0-prerelease.222 18 Sep 2026 none MIT — Details →
6.0.0-prerelease.194 18 Sep 2026 none MIT — Details →
6.0.0-prerelease.192 16 Sep 2026 none MIT — Details →
6.0.0-prerelease.187 16 Sep 2026 none MIT — Details →
6.0.0-prerelease.186 16 Sep 2026 none MIT — Details →
6.0.0-prerelease.185 16 Sep 2026 none MIT — Details →
6.0.0-prerelease.184 16 Sep 2026 none MIT — Details →
6.0.0-prerelease.183 16 Sep 2026 none MIT — Details →
6.0.0-prerelease.181 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.180 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.179 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.178 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.165 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.169 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.160 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.149 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.141 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.128 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.135 13 Sep 2026 none MIT — Details →
6.0.0-prerelease.114 12 Sep 2026 none MIT — Details →
6.0.0-prerelease.82 12 Sep 2026 none MIT — Details →
6.0.0-prerelease.81 21 Aug 2026 none MIT — Details →
6.0.0-prerelease.79 10 Aug 2026 none MIT — Details →
6.0.0-prerelease.80 10 Aug 2026 none MIT — Details →
6.0.0-prerelease.77 27 Feb 2026 none MIT — Details →
6.0.0-prerelease.76 27 Feb 2026 none MIT — Details →
6.0.0-prerelease.75 29 Jan 2026 none MIT — Details →
6.0.0-prerelease.74 28 Dec 2025 none MIT — Details →
6.0.0-prerelease.73 28 Oct 2025 none MIT — Details →
6.0.0-prerelease.71 28 Oct 2025 none MIT — Details →
6.0.0-prerelease.67 26 Oct 2025 none MIT — Details →
6.0.0-prerelease.66 26 Oct 2025 none MIT — Details →
6.0.0-prerelease.65 08 Oct 2025 none MIT — Details →
6.0.0-prerelease.64 08 Oct 2025 none MIT — Details →
6.0.0-prerelease.63 07 Oct 2025 none MIT — Details →
6.0.0-prerelease.62 05 Oct 2025 none MIT — Details →
6.0.0-prerelease.57 05 Oct 2025 none MIT — Details →
6.0.0-prerelease.56 05 Oct 2025 none MIT — Details →
6.0.0-prerelease.55 01 Oct 2025 none MIT — Details →
6.0.0-prerelease.53 01 Oct 2025 none MIT — Details →
6.0.0-prerelease.52 30 Sep 2025 none MIT — Details →
6.0.0-prerelease.51 28 Sep 2025 none MIT — Details →
6.0.0-prerelease.50 28 Sep 2025 none MIT — Details →
6.0.0-prerelease.49 27 Sep 2025 none MIT — Details →
6.0.0-prerelease.48 27 Sep 2025 none MIT — Details →
6.0.0-prerelease.47 27 Sep 2025 none MIT — Details →
6.0.0-prerelease.9 20 Sep 2025 none MIT — Details →
5.0.21 05 Jul 2024 none MIT — Details →
5.0.20 04 Jun 2024 none MIT — Details →
5.0.17 21 Jul 2023 none non-standard — Details →
5.0.16 10 Mar 2023 none non-standard — Details →
5.0.15 23 Dec 2022 none non-standard — Details →
5.0.14 16 Dec 2022 none non-standard — Details →
5.0.13 08 Dec 2022 none non-standard — Details →
5.0.12 15 Jun 2022 C1 non-standard Yes Details →
5.0.11 23 Jul 2021 C1 non-standard Yes Details →
5.0.10 09 Jan 2021 C1 non-standard Yes Details →
5.0.9 06 Aug 2020 C1 non-standard Yes Details →
5.0.8 13 May 2020 C1 non-standard Yes Details →
5.0.7 14 Apr 2020 C1 non-standard Yes Details →
5.0.5 26 Mar 2020 C1 non-standard Yes Details →
5.0.4 12 Mar 2020 C1 non-standard Yes Details →
5.0.3 21 Feb 2020 C1 non-standard Yes Details →
5.0.2 10 Feb 2020 C1 non-standard Yes Details →
5.0.1 03 Feb 2020 C1 non-standard Yes Details →
5.0.0-rc 19 Jan 2020 C1 non-standard Yes Details →
5.0.0-beta 29 Oct 2019 C1 non-standard Yes Details →
5.0.0-alpha2 24 Sep 2019 C1 non-standard Yes Details →
5.0.0-alpha 04 Aug 2019 C1 non-standard Yes Details →
4.1.4 11 Jun 2018 C1 non-standard Yes Details →
4.1.3 28 May 2018 C1 non-standard Yes Details →
3.1.5 17 Mar 2018 C1 — Yes Details →
4.1.2 11 Mar 2018 C1 non-standard Yes Details →
4.1.1 08 Jan 2018 C1 non-standard Yes Details →
4.1.0 17 Dec 2017 C1 non-standard Yes Details →
4.0.0 18 Oct 2017 C1 non-standard Yes Details →
4.0.0-beta2 02 Oct 2017 C1 — Yes Details →
4.0.0-beta1 28 Aug 2017 C1 — Yes Details →
3.1.4 16 Aug 2017 C1 — Yes Details →
3.1.3 13 Aug 2017 C1 — Yes Details →
3.1.2 04 Aug 2017 C1 — Yes Details →
3.1.1 08 Jun 2017 C1 — Yes Details →
3.1.0 11 Mar 2017 C1 — Yes Details →
3.0.1 15 Feb 2017 C1 — Yes Details →
3.0.0 20 Jan 2017 C1 — Yes Details →
3.0.0-beta3 25 Dec 2016 C1 — Yes Details →
3.0.0-beta2 27 Nov 2016 C1 — Yes Details →
3.0.0-beta 20 Nov 2016 C1 — Yes Details →
2.0.4 07 Nov 2016 C1 — Yes Details →
2.0.2 25 Aug 2016 C1 — Yes Details →
2.0.1 22 Aug 2016 C1 — Yes Details →
2.0.0 31 Jul 2016 C1 — Yes Details →
1.0.5 23 Jul 2016 C1 — Yes Details →
2.0.0-rc2 20 Jul 2016 C1 — Yes Details →
2.0.0-rc 24 Dec 2015 C1 — Yes Details →
2.0.0-beta 20 Nov 2015 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for LiteDB

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 LiteDB

Is LiteDB safe to use?

Vulert records 1 vulnerabilities for LiteDB in NuGet: 1 critical, 0 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 LiteDB's Vulert package health score?

Vulert scores LiteDB 80/100, which reads as in good shape. 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 LiteDB affected?

No. 5.0.21, 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 LiteDB should I use?

5.0.21 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 LiteDB have?

1 vulnerability is recorded for LiteDB in the NuGet ecosystem: 1 critical, 0 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 LiteDB vulnerabilities disclosed?

0 vulnerabilities were recorded for LiteDB in the last 12 months, and the oldest entry in this database dates to 24 Feb 2023. 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 LiteDB 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 LiteDB for upcoming vulnerabilities?

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