---
id: "CVE-2026-64678"
page: "https://infrastack.ai/live/CVE-2026-64678"
kind: "vulnerability"
aliases: ["CVE-2026-64678"]
title: "Nitrite database: legacy file migration deserializes untrusted data, enabling code execution"
severity: "critical"
cvss: 9.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["embedded-database", "java", "nitrite", "package"]
not_affected_if: ["only-trusted-database-files", "version-4.4.1-or-later"]
published_at: "2026-11-11T05:19:51+00:00"
first_seen_at: "2026-11-11T05:25:40+00:00"
updated_at: "2026-11-11T05:26:35+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64678", "first_seen_at": "2026-11-11T05:25:40+00:00"}]
exploit_sources: []
---

# Nitrite database: legacy file migration deserializes untrusted data, enabling code execution

Link for people: https://infrastack.ai/live/CVE-2026-64678 (this .md is for agents)

Nitrite, a Java embedded NoSQL document store, automatically deserializes stored values with Java's ObjectInputStream when it opens an old-format database file, with no class allowlist. An attacker who can supply a crafted database file, and who has a suitable gadget class on the classpath, can run code in the host application.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Nitrite version in the project's build file (for example `pom.xml` or `build.gradle`) or the dependency tree; a version below `4.4.1` is affected
- Check whether the application opens database files that could come from outside the trust boundary, such as user uploads or files from other systems

## Fix

- Nitrite: upgrade to `4.4.1` or later

## Timeline

- 2026-11-11T05:25:40+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-64678

## Documents

- [advisory] Vendor advisory: github.com https://github.com/nitrite/nitrite-java/security/advisories/GHSA-9297-g93h-86gg
- [fix] Release notes: github.com https://github.com/nitrite/nitrite-java/releases/tag/v4.4.1

## From the sources

NOsql Object (NO2 a.k.a Nitrite) database is an open source nosql embedded document store. Prior to version 4.4.1, when Nitrite opens a database file, MVStoreUtils.openOrCreate() automatically checks for a legacy v1-format store and, on detecting one (or hitting a compatibility error while opening), triggers an automatic migration path. This path deserializes stored values using NitriteDataType.deserialize(byte[]), which passes the raw bytes directly to java.io.ObjectInputStream.readObject() via a custom NitriteObjectInputStream subclass. That subclass overrides only readClassDescriptor() — solely to remap a handful of known legacy class names to their current equivalents — and implements no class allowlist, blocklist, or ObjectInputFilter (JEP 290). Any Serializable class reachable on the embedding application's classpath can therefore be instantiated via readObject(), with readObject()/readExternal()/readResolve() callbacks invoked unconditionally. If a suitable gadget class (e.g. from commons-collections or similar) happens to be present on the classpath, this is a precondition for remote code execution. This issue has been patched in version 4.4.1.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_