GHSA-85qj-f5wg-rwp9
Spring Statemachine's Kryo-based persistence backends deserialize persisted state-machine contexts without enforcing a class allowlist
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.springframework.statemachine:spring-statemachine-kryo | >= 3.2.0, <= 3.2.4 | no fix listed |
| Maven | org.springframework.statemachine:spring-statemachine-kryo | >= 4.0.0, < 4.0.2 | 4.0.2 |
Details
As written in the advisory (Markdown source, shown as plain text).
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
References
External links from the advisory. They lead to third-party sites.
- https://nvd.nist.gov/vuln/detail/CVE-2026-41862
- https://github.com/spring-attic/spring-statemachine/commit/6b77ea6b729e5346d83e31f36c43818665d67384
- https://github.com/spring-attic/spring-statemachine
- https://github.com/spring-attic/spring-statemachine/releases/tag/v4.0.2
- https://spring.io/security/cve-2026-41862