Skip to main content
VulnerabilityPublished

CVE-2026-41862: Spring Statemachine · Deserialization of Untrusted Data

Affects Spring StatemachineSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 4.0.1.1 or 3.2.5 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.1.1, 3.2.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Spring Statemachine to 4.0.1.1 or 3.2.5.

Affected software

ProductAffectedFixed in
SpringSpring StatemachineAffected
  • >=4.0.0 <4.0.1.1
Fixed in
  • 4.0.1.1
SpringSpring StatemachineAffected
  • >=3.2.0 <3.2.5
Fixed in
  • 3.2.5
Mavenorg.springframework.statemachine/statemachine-corepkg:maven/org.springframework.statemachine/statemachine-coreOther threatsAffected
  • =3.2.0
  • <=3.2.4
  • =4.0.0
  • <=4.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider disabling or restricting use of Kryo-based persistence backends in Spring Statemachine or applying custom deserialization allowlists if feasible.

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

References

Community reviews

Loading reviews…