Deserialization of Untrusted Data Affecting org.springframework.statemachine:spring-statemachine-core package, versions [,4.0.2)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.76% (54th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JAVA-ORGSPRINGFRAMEWORKSTATEMACHINE-18353355
  • published28 Jul 2026
  • disclosed11 Jun 2026
  • creditUnknown

Introduced: 11 Jun 2026

CVE-2026-41862  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade org.springframework.statemachine:spring-statemachine-core to version 4.0.2 or higher.

Overview

org.springframework.statemachine:spring-statemachine-core is a

Affected versions of this package are vulnerable to Deserialization of Untrusted Data. The Kryo-based persistence serializers (KryoStateMachineSerialisationService / AbstractKryoStateMachineSerialisationService) deserialise persisted state-machine contexts without enabling Kryo.setRegistrationRequired(true) or enforcing a class allowlist. This affects every persistence backend that round-trips the StateMachineContext through Kryo, namely the JPA, MongoDB, Redis and ZooKeeper persisters. An attacker who can write to or tamper with the persisted context store can supply a serialized payload referencing arbitrary classes, triggering a deserialization gadget chain that results in remote code execution inside the application JVM.

Note:

Exploitation requires the attacker to be able to control or modify the contents of the persistence store (database, Redis, MongoDB or ZooKeeper node) from which contexts are loaded.

CVSS Base Scores

version 4.0
version 3.1