Unsafe Java deserialization in Nitrite legacy v1 migration path
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-502.
Summary
Nitrite (nitrite-java) before 4.4.1 deserializes stored values during its automatic migration of legacy v1 databases without restricting which classes can be loaded. This unsafe deserialization (CWE-502) lets an unauthenticated remote attacker cause any Serializable class on the application classpath to be instantiated. If a suitable gadget class is present, this can lead to remote code execution.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Update nitrite-java to version 4.4.1, the fixed version.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · CNA nitrite-java (nitrite) Fixed in 4.4.1
Timeline
- 2026-11-11 Threatist record created from CVE-2026-64678
- 2026-11-12 CISA SSVC decision points changed
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences