LiteDB may deserialize bad JSON on object type using _type

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-23535: 0.70% estimated exploitation activity in the next 30 days; percentile 53.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact LiteDB use a special field in JSON documents to cast diferent types from BsonDocument do POCO classes. When instance of an object are not the same of class, BsonMapper use a special field type string info with full class name with assembly to be loaded and fit in your model. If your end-user can send to your app a plain JSON string, deserialization can load an unsafe object to fit in your model. Patches Version = 5.0.13 add some basic fixes to avoid this, but is not 100% guaranteed when using Object type Next major version will contains a allow-list to select what king of Assembly can be loaded Workarounds - Avoid users send to your app a JSON string to be direct insert/update into database - Avoid use classes with Object type - try use an interface when possible If your app send a plain JSON string to be insert/update into database, prefer this: References See this workaround fix on this commit: https://github.com/mbdavid/LiteDB/commit/4382ff4dd0dd8b8b16a4e37dfd29727c5f70f93f

Published by the source

24 Feb 2023, 16:22 UTC

Last modified by the source

6 Mar 2023, 22:00 UTC

Source last checked

26 Oct 2026, 16:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3x49-g6rc-c284

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-23535

Advisory: LiteDB may deserialize bad JSON on object type using _type
IDs: CVE-2022-23535, GHSA-3x49-g6rc-c284
Record: https://patchnext.com/advisories/cve-2022-23535 (revision 1, source checked 26 Oct 2026, 16:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: litedb 5.0.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet litedb: affected < 5.0.13; fixed in 5.0.13

## Suggested inspection (read-only)
- NuGet litedb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on litedb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3x49-g6rc-c284 (GitHub-reviewed advisory GHSA-3x49-g6rc-c284 lists affected ranges: NuGet litedb >=0 <5.0.13)

Commands are suggestions: review each one before running it.