CVE-2026-41862 is a high-severity (CVSS 8.8) Deserialization of Untrusted Data vulnerability in org.springframework.statemachine:spring-statemachine-kryo. A fix is available for org.springframework.statemachine:spring-statemachine-kryo — see the affected versions and patch details below.
Spring Statemachine's Kryo-based persistence backends deserialize persisted state-machine contexts without enforcing a class allowlist
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41862.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41862 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.statemachine:spring-statemachine-kryo☕org.springframework.statemachine:spring-statemachine-kryoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.statemachine:spring-statemachine-kryo | ≥ 3.2.0 | No fix |
| ☕Maven | org.springframework.statemachine:spring-statemachine-kryo | ≥ 4.0.0&&< 4.0.2 | 4.0.2org.springframework.statemachine:spring-statemachine-kryo:4.0.2 |
Affected Products
spring statemachinebroadcomDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.statemachine:spring-statemachine-kryo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.springframework.statemachine:spring-statemachine-kryo has shipped for CVE-2026-41862 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2026-41862 in your dependencies?
Find it across Maven, including transitive dependencies.