Unsafe Deserialization in org.springframework.statemachine:spring-statemachine-kryo (CVE-2026-41862)
Summary
Vulnerability in org.springframework.statemachine:spring-statemachine-kryo (CVE-2026-41862). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.0.2 or later.
Original description
The description as published by the source.
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
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41862 has been found in org.springframework.statemachine:spring-statemachine-kryo.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade org.springframework.statemachine:spring-statemachine-kryo to 4.0.2 or later.
If unsure, ask your IT team or search "org.springframework.statemachine:spring-statemachine-kryo CVE-2026-41862" on the vendor's site.
CVE-2026-41862 (org.springframework.statemachine:spring-statemachine-kryo) — CWE-502 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in org.springframework.statemachine:spring-statemachine-kryo.
Check the vendor advisory for the affected versions of org.springframework.statemachine:spring-statemachine-kryo.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 4.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springframework.statemachine:spring-statemachine-kryo を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springframework.statemachine:spring-statemachine-kryo to 4.0.2ステージング環境で 4.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web spring.io
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com