AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 31 Bitcoin

fix regresssion of json wallet serialization with jdk25

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
fix regresssion of json wallet serialization with jdk25
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a regression in how Sparrow Wallet saves and loads wallet data as JSON when running on newer Java versions (JDK 25). Previously, the app relied on a deep Java reflection trick to serialize certain objects, which no longer works in JDK 25. The fix removes that fragile dependency and explicitly tells the JSON library how to construct and serialize each wallet-related class. It is a compatibility/maintenance fix, not a patch for an active security vulnerability, but it touches code that handles encrypted wallet data and private-key material, so correctness matters for user safety.

Recommended action

Treat as a routine compatibility fix with security-adjacent risk. Review that each new InstanceCreator produces a valid default object that Gson can safely populate via reflection, and verify round-trip serialization tests pass for all wallet types. No urgent security patch is indicated, but ensure the change is included in the next release to avoid data-loss or startup failures on JDK 25.

Security signals we found

01

Touches serialization/deserialization of encrypted wallet structures (EncryptedData, DeterministicSeed, MasterPrivateExtendedKey)

02

Removes JVM reflective openness for java.base/java.io to Gson

03

Adds explicit instance creators for classes that previously relied on sun.misc.Unsafe fallback

04

Disables Gson JdkUnsafe to make tests fail consistently with production behavior

05

Fixes a regression that could prevent wallet JSON persistence from functioning on JDK 25

Risk score

Why this scored 31/100

Our methodology →
Potential impact 8/30
Exploitability 4/25
Stealth signal 3/15
Affected reach 6/15
Confidence 7/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.