CVE-2026-41862: CWE-502: Deserialization of Untrusted Data in Spring Spring Statemachine
Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis and ZooKeeper) deserialise persisted state-machine contexts without enforcing a class allowlist (CWE-502, deserialisation of untrusted data), which can lead to remote code execution inside the application JVM. Affected versions: Spring Statemachine 4.0.0 through 4.0.1 Spring Statemachine 3.2.0 through 3.2.4
AI Analysis
Technical Summary
CVE-2026-41862 affects Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis, and ZooKeeper) in versions 3.2.0 through 3.2.4 and 4.0.0 through 4.0.1. These backends deserialize persisted state-machine contexts without enforcing a class allowlist, leading to deserialization of untrusted data (CWE-502). This flaw can enable remote code execution inside the JVM running the application. The vulnerability has a CVSS 3.1 base score of 8.8, indicating high severity. No vendor advisory or patch information is currently available, and no known exploits in the wild have been reported.
Potential Impact
Successful exploitation allows an attacker with at least low privileges to cause remote code execution within the application JVM by exploiting unsafe deserialization of persisted state-machine contexts. This can lead to full compromise of the affected application environment, including confidentiality, integrity, and availability impacts.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, consider disabling or restricting use of Kryo-based persistence backends in Spring Statemachine or applying custom deserialization allowlists if feasible. Monitor vendor channels for updates.
CVE-2026-41862: CWE-502: Deserialization of Untrusted Data in Spring Spring Statemachine
Description
Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis and ZooKeeper) deserialise persisted state-machine contexts without enforcing a class allowlist (CWE-502, deserialisation of untrusted data), which can lead to remote code execution inside the application JVM. Affected versions: Spring Statemachine 4.0.0 through 4.0.1 Spring Statemachine 3.2.0 through 3.2.4
CVSS v3.1
Score 8.8high
Affected software
pkg:maven/org.springframework.statemachine/statemachine-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41862 affects Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis, and ZooKeeper) in versions 3.2.0 through 3.2.4 and 4.0.0 through 4.0.1. These backends deserialize persisted state-machine contexts without enforcing a class allowlist, leading to deserialization of untrusted data (CWE-502). This flaw can enable remote code execution inside the JVM running the application. The vulnerability has a CVSS 3.1 base score of 8.8, indicating high severity. No vendor advisory or patch information is currently available, and no known exploits in the wild have been reported.
Potential Impact
Successful exploitation allows an attacker with at least low privileges to cause remote code execution within the application JVM by exploiting unsafe deserialization of persisted state-machine contexts. This can lead to full compromise of the affected application environment, including confidentiality, integrity, and availability impacts.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, consider disabling or restricting use of Kryo-based persistence backends in Spring Statemachine or applying custom deserialization allowlists if feasible. Monitor vendor channels for updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-22T06:22:10.082Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3af602eed863c81e9ec620
Added to database: 06/23/2026, 21:09:22 UTC
Last enriched: 06/30/2026, 23:16:50 UTC
Last updated: 08/07/2026, 12:41:11 UTC
Views: 143
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.