Widely-used Spring Statemachine; RCE via untrusted deserialization could impact many Java apps.
CVE-2026-41862
RCE via Kryo deserialization in Spring Statemachine persistence backends.
Is CVE-2026-41862 being exploited?
Not confirmed. CVE-2026-41862 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.75% probability of exploitation in the next 30 days.
How severe is CVE-2026-41862?
CVE-2026-41862 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41862?
Not known from our data. No patch reference has been recorded for CVE-2026-41862, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-41862 affect?
CVE-2026-41862 affects Spring Statemachine 4.0.0-4.0.1, Spring Statemachine 3.2.0-3.2.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41862?
Upgrade to fixed version when released; monitor advisories
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via deserializing untrusted state-machine contexts in Kryo backends (JPA, Mongo, Redis, ZooKeeper).
Patch when available
- affected>= 4.0.0 and < 4.0.1.1
- affected>= 3.2.0 and < 3.2.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.