CVE-2026-64678: Unsafe Java Deserialization in Nitrite Legacy Database Migration
Nitrite (NOsql Object, also known as NO2) versions before 4.4.1 contain an unsafe Java deserialization vulnerability in automatic migration of legacy v1 database stores. When MVStoreUtils.openOrCreate() detects a legacy store or encounters a compatibility error while opening a database, it can trigger migration. This path invokes NitriteDataType.deserialize(byte[]), which passes stored bytes to ObjectInputStream.readObject() through NitriteObjectInputStream. The subclass only remaps certain legacy class descriptors and provides no class allowlist, blocklist, or JEP 290 ObjectInputFilter. Consequently, attacker-controlled serialized values can instantiate classes available on the embedding application's classpath and invoke deserialization callbacks, potentially enabling arbitrary code execution when a suitable gadget chain is present.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can execute arbitrary code with the privileges of the embedding application, potentially compromising its accessible data, modifying application or database state, and disrupting service. Code execution depends on attacker-controlled serialized data reaching the migration path and suitable gadget classes being available on the application classpath; it is not an unconditional consequence of opening every legacy database.
Mitigation
If you can’t patch tonight, do this now.
Until the upgrade is deployed, prevent applications from opening attacker-supplied or attacker-modifiable Nitrite database stores, particularly legacy v1 stores that trigger automatic migration. Restrict database import and replacement capabilities to trusted sources. Review and minimize dependencies that supply deserialization gadgets; removing known gadgets reduces risk but does not fix the underlying unfiltered deserialization.
Remediation
Patch, then assume compromise.
Upgrade Nitrite to version 4.4.1 or later, which includes the fix. Review the embedding application's classpath for vulnerable deserialization gadget classes and update or remove affected dependencies as appropriate.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-64678 exploited in the wild?
- As of Nov 12, 2026, Mallory has no reports of CVE-2026-64678 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-64678?
- Yes. As of Nov 12, 2026, Mallory has reports of a public exploit for CVE-2026-64678.
- Is there a patch for CVE-2026-64678?
- Upgrade Nitrite to version 4.4.1 or later, which includes the fix. Review the embedding application's classpath for vulnerable deserialization gadget classes and update or remove affected dependencies as appropriate.
- How severe is CVE-2026-64678?
- CVE-2026-64678 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 0.66% (52nd percentile) as of Nov 12, 2026.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.