CVE-2026-41862
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring Statemachine's Kryo-based persistence backends (JPA, MongoDB, Redis, ZooKeeper) deserialize persisted state-machine contexts without validating against a class allowlist, allowing attackers to inject malicious serialized objects that execute arbitrary code within the application JVM.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Spring Statemachine is in useSearch your project dependencies for spring-statemachine-core or review your application's runtime classpath for org.springframework.statemachine classesAffected if Spring Statemachine library is present in the application
-
Determine the installed Spring Statemachine versionReview your build configuration (Maven pom.xml, Gradle build.gradle) or check the spring-statemachine-core JAR manifest for the version numberAffected if The version is below 3.2.5 or 4.0.2 (e.g., 3.x versions below 3.2.5, 4.x versions below 4.0.2)
-
Identify if Kryo-based persistence is enabledSearch configuration files and code for persistence backend configuration: look for StateMachineJpaRepository, StateMachineMongoDbRepository, StateMachineRedisRepository, or StateMachineZooKeeperRepository bean definitions or propertiesAffected if One or more of these Kryo-backed persistence repositories are configured and active in the application context
-
Check if custom allowlist serializer is implementedSearch project code for custom KryoSerializer implementations or BeanFactoryBeanResolver configurations that define allowed classes for deserializationAffected if No custom serializer with explicit class allowlist is found; the application relies on default Kryo deserialization for state machine context
The environment is affected if Spring Statemachine with a Kryo-based persistence backend (JPA, MongoDB, Redis, or ZooKeeper) is in use and the version is below 3.2.5 or 4.0.2 without a custom allowlist serializer in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Spring Statemachine 4.0.2+ or 3.2.5+ which implement class allowlisting for Kryo deserialization. If upgrades are not immediately possible, implement a custom Kryo Serializer that enforces an explicit allowlist of permitted classes for the state machine context.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41862 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data