CVE-2026-41862: Spring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis and ZooKeeper) deserialise persiste

This month

HIGH 8.8UPGRADE

CVE-2026-41862 is a high-severity flaw (CVSS 8.8) affecting spring statemachine. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-06-23
Last modified	2026-10-25

Publisher (CNA): VMware · Vendor: broadcom

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-23 21:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

broadcom spring statemachine UPGRADE

Affected: >= 3.2.0 and < 3.2.5 · >= 4.0.0 and < 4.0.2

Fixed in: 3.2.5, 4.0.2

Safe to downgrade to: a release before 3.2.0

1. Check installed version

apt-cache policy spring-statemachine || rpm -q spring-statemachine || spring-statemachine --version

2. UPGRADE to 3.2.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-statemachine

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-statemachine

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.2.0 (Debian / Ubuntu)

apt-cache madison spring-statemachine sudo apt install spring-statemachine=<VERSION_BEFORE_3.2.0> sudo apt-mark hold spring-statemachine

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-statemachine sudo dnf downgrade spring-statemachine-<VERSION_BEFORE_3.2.0> sudo dnf versionlock add spring-statemachine

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41862?

spring statemachine: upgrade to 3.2.5, 4.0.2. Exact commands for each OS are on this page.

Is CVE-2026-41862 being exploited?

CVE-2026-41862 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41862 affect?

CVE-2026-41862 affects spring statemachine. Severity is high (CVSS 8.8). 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 remot

How urgent is CVE-2026-41862?

Priority 45/100. High severity

Software pages

MongoDB vulnerabilities · Redis vulnerabilities · Apache ZooKeeper vulnerabilities

References

← Back to latest CVEs