Is LiteDB 5.0 vulnerable?
NuGet · 18 releases from 5.0.1 to 5.0.21 · latest LiteDB is 5.0.21 · checked 18 Nov 2026
No known advisories in the last release
LiteDB 5.0.21, the last 5.0 release, has no known advisories. 1 advisory affects earlier 5.0.x releases, so update to 5.0.21.
dotnet add package LiteDB --version 5.0.21Is your project on an affected LiteDB?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 5.0.x, affecting earlier releases
LiteDB may deserialize bad JSON on object type using _type
- Affected
- <5.0.13
- Fixed in
- 5.0.13
Every LiteDB 5.0.x release
Affected: 5.0.1 to 5.0.12. 5.0.13 and later are not affected.
| Version | Known advisories |
|---|---|
| LiteDB 5.0.21 | None |
| LiteDB 5.0.20 | None |
| LiteDB 5.0.17 | None |
| LiteDB 5.0.16 | None |
| LiteDB 5.0.15 | None |
| LiteDB 5.0.14 | None |
| LiteDB 5.0.13 | None |
| LiteDB 5.0.12 | CVE-2022-23535 |
| LiteDB 5.0.11 | CVE-2022-23535 |
| LiteDB 5.0.10 | CVE-2022-23535 |
| LiteDB 5.0.9 | CVE-2022-23535 |
| LiteDB 5.0.8 | CVE-2022-23535 |
| LiteDB 5.0.7 | CVE-2022-23535 |
| LiteDB 5.0.5 | CVE-2022-23535 |
| LiteDB 5.0.4 | CVE-2022-23535 |
| LiteDB 5.0.3 | CVE-2022-23535 |
| LiteDB 5.0.2 | CVE-2022-23535 |
| LiteDB 5.0.1 | CVE-2022-23535 |
Which of your client projects are still on LiteDB 5.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact LiteDB version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other LiteDB versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.