CVE-2026-41862
Spring Statemachine Deserialisation Vulnerability
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
INFO
Published Date :
June 23, 2026, 8:59 p.m.
Last Modified :
June 23, 2026, 8:59 p.m.
Remotely Exploit :
Yes !
Source :
vmware
Affected Products
The following products are affected by CVE-2026-41862
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | dcf2e128-44bd-42ed-91e8-88f912c1401d |
Solution
- Update Spring Statemachine to version 4.0.2 or later.
- Update Spring Statemachine to version 3.2.5 or later.
- Ensure class allowlisting is enforced for Kryo deserialisation.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-41862 vulnerability anywhere in the article.