GHSA-85qj-f5wg-rwp9
Spring Statemachine's Kryo-based persistence backends deserialize persisted state-machine contexts without enforcing a class allowlist
Quick fix
GHSA-85qj-f5wg-rwp9 — org.springframework.statemachine:spring-statemachine-kryo: upgrade to the fixed version with the command below.
# pom.xml: bump <version>4.0.2</version> for org.springframework.statemachine:spring-statemachine-kryoDetails
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
Are you affected?
Enter the version of the package you're using.
Affected packages
3.2.0No fixed version published yet for org.springframework.statemachine:spring-statemachine-kryo (maven). Pin to a known-safe version or switch to an alternative.
4.0.0Fixed in: 4.0.2# pom.xml: bump <version>4.0.2</version> for org.springframework.statemachine:spring-statemachine-kryoReferences
- https://nvd.nist.gov/vuln/detail/CVE-2026-41862[ADVISORY]
- https://github.com/spring-attic/spring-statemachine/commit/6b77ea6b729e5346d83e31f36c43818665d67384[WEB]
- https://github.com/spring-attic/spring-statemachine[PACKAGE]
- https://github.com/spring-attic/spring-statemachine/releases/tag/v4.0.2[WEB]
- https://spring.io/security/cve-2026-41862[WEB]