GitHub Advisoryadvisory · Maven

GHSA-85qj-f5wg-rwp9 Spring Statemachine's Kryo-based persistence backends deserialize persisted state-machine contexts without enforcing a class allowlist

HIGH Published 2026-06-23 Modified 2026-09-24 Official page ↗
Aliases
CVE-2026-41862
Ecosystem
Maven
Packages
org.springframework.statemachine:spring-statemachine-kryo
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-502
Reviewed
2026-09-24

Affected packages

• Maven org.springframework.statemachine:spring-statemachine-kryo: >= 3.2.0, <= 3.2.4 (no fix yet) • Maven org.springframework.statemachine:spring-statemachine-kryo: >= 4.0.0, < 4.0.2 → fixed in 4.0.2

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

Related

Alias · CVE (1)

  • CVE-2026-41862 Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis and ZooKeeper) deserialise persisted state-machine contexts… vulnerability

Weakness · CWE (1)

  • CWE-502 Deserialization of Untrusted Data weakness

References