published 23 Jun 2026 · updated 24 Jun 2026
Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis and ZooKeeper) deserialise persisted state-machine contexts…
8.8HighCVSS 8.8EPSS 1%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.2.5 and 4.0.1.1.
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
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=3.2.0 <3.2.5, >=4.0.0 <4.0.1.1 | 3.2.5, 4.0.1.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket