CVE-2026-41862 Spring CVE debrief

Who should care

Defenders and security teams responsible for Spring Statemachine deployments should assess exposure and apply patches or updates to prevent potential remote code execution. This includes verifying if the application uses affected Spring Statemachine versions, reviewing compensating controls, and tracking exceptions. Security teams should also prioritize verifying exposure and applying patches for Spring Statemachine versions 3.2.0 through 3.2.4 and 4.0.0

Why it matters

CVE-2026-41862 is a high-severity vulnerability in Spring Statemachine's Kryo-based persistence backends, which can lead to remote code execution. Defenders should prioritize verifying exposure and applying patches for affected versions.

• Remote code execution inside the application JVM
• Potential data breaches or system compromise
• Need for verification of exposure and patch application
• Possible disruption of business operations

Technical summary

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. The vulnerability affects Spring Statemachine versions 3.2.0 through 3.2.4 and 4.0.0 through 4.0.1. Defenders should prioritize verifying exposure and applying patches for affected versions to prevent potential remote code execution. This vulnerability has a high-severity CVSS score of 8.8.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for Spring Statemachine versions 3.2.0 through 3.2.4 and 4.0.0 through 4.0.1.

Recommended defensive actions

• Verify if the application uses affected Spring Statemachine versions and assess exposure
• Apply patches or updates to Spring Statemachine versions 3.2.0 through 3.2.4 and 4.0.0 through 4.0.1
• Implement additional security measures to restrict deserialisation of untrusted data
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Spring Statemachine's Kryo-based persistence backends, which deserialise persisted state-machine contexts without enforcing a class allowlist, potentially leading to remote code execution.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.