Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.springframework.statemachine:spring-statemachine-kryo

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.8MavenPublished

    Spring Statemachine's Kryo-based persistence backends deserialize persisted state-machine contexts without enforcing a class allowlist

    CVE-2026-41862 · GHSA-85qj-f5wg-rwp9

    Affected
    • Maven org.springframework.statemachine:spring-statemachine-kryo >= 3.2.0, <= 3.2.4; >= 4.0.0, <= 4.0.1
    Fixed in
    4.0.2· Partial vendor fix
    Issue
    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

    Recommended action: Upgrade to 4.0.2; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →