CVE-2026-41862

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-23. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

CVE-2026-41862: Kryo deserialization of persisted context without class allowlist

https://spring.io/security/cve-2026-41862

Vendor Advisories for CVE-2026-41862(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 77× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 03:53 UTCGHSA enrichment
  2. 2026-07-26 15:51 UTCEG score recompute
  3. 2026-07-26 15:51 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:11 UTCEG score recompute
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:24 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-17 05:38 UTCGHSA enrichment
  16. 2026-07-16 17:52 UTCGHSA enrichment
  17. 2026-07-16 17:03 UTCEPSS rescore
  18. 2026-07-16 05:47 UTCGHSA enrichment
  19. 2026-07-15 18:00 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 06:14 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 16:28 UTCGHSA enrichment
  24. 2026-07-14 04:42 UTCGHSA enrichment
  25. 2026-07-13 22:30 UTCEPSS rescore
Show 64 more
  1. 2026-07-13 16:54 UTCGHSA enrichment
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 04:19 UTCGHSA enrichment
  5. 2026-07-12 16:16 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 04:29 UTCGHSA enrichment
  8. 2026-07-11 16:43 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 04:57 UTCGHSA enrichment
  11. 2026-07-10 17:09 UTCGHSA enrichment
  12. 2026-07-10 05:22 UTCGHSA enrichment
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 17:33 UTCGHSA enrichment
  15. 2026-07-09 05:40 UTCGHSA enrichment
  16. 2026-07-08 17:54 UTCGHSA enrichment
  17. 2026-07-08 15:15 UTCEPSS rescore
  18. 2026-07-08 06:05 UTCGHSA enrichment
  19. 2026-07-07 18:16 UTCGHSA enrichment
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-07 06:29 UTCGHSA enrichment
  22. 2026-07-06 18:41 UTCGHSA enrichment
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 06:44 UTCGHSA enrichment
  26. 2026-07-06 02:23 UTCEPSS rescore
  27. 2026-07-06 02:23 UTCEPSS rescore
  28. 2026-07-05 18:58 UTCGHSA enrichment
  29. 2026-07-05 07:12 UTCGHSA enrichment
  30. 2026-07-05 02:30 UTCEPSS rescore
  31. 2026-07-04 19:20 UTCGHSA enrichment
  32. 2026-07-04 07:34 UTCGHSA enrichment
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-03 19:46 UTCGHSA enrichment
  35. 2026-07-03 08:00 UTCGHSA enrichment
  36. 2026-07-02 20:13 UTCGHSA enrichment
  37. 2026-07-02 08:24 UTCGHSA enrichment
  38. 2026-07-01 20:38 UTCGHSA enrichment
  39. 2026-07-01 15:06 UTCEPSS rescore
  40. 2026-07-01 08:51 UTCGHSA enrichment
  41. 2026-06-30 23:22 UTCEPSS rescore
  42. 2026-06-30 21:05 UTCGHSA enrichment
  43. 2026-06-30 09:16 UTCGHSA enrichment
  44. 2026-06-29 21:30 UTCGHSA enrichment
  45. 2026-06-29 14:06 UTCEPSS rescore
  46. 2026-06-29 09:43 UTCGHSA enrichment
  47. 2026-06-28 21:55 UTCGHSA enrichment
  48. 2026-06-28 14:07 UTCEPSS rescore
  49. 2026-06-28 10:08 UTCGHSA enrichment
  50. 2026-06-28 04:56 UTCEPSS rescore
  51. 2026-06-27 22:22 UTCGHSA enrichment
  52. 2026-06-27 10:36 UTCGHSA enrichment
  53. 2026-06-27 03:08 UTCEPSS rescore
  54. 2026-06-26 22:49 UTCGHSA enrichment
  55. 2026-06-26 11:04 UTCGHSA enrichment
  56. 2026-06-25 21:38 UTCGHSA enrichment
  57. 2026-06-25 13:49 UTCEPSS rescore
  58. 2026-06-25 13:49 UTCEPSS rescore
  59. 2026-06-25 09:51 UTCGHSA enrichment
  60. 2026-06-24 22:05 UTCGHSA enrichment
  61. 2026-06-24 14:05 UTCEPSS rescore
  62. 2026-06-24 10:17 UTCGHSA enrichment
  63. 2026-06-23 22:30 UTCEG score recompute
  64. 2026-06-23 22:30 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41862?
CVE-2026-41862 is a high vulnerability published on June 23, 2026. 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…
When was CVE-2026-41862 disclosed?
CVE-2026-41862 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41862 actively exploited?
CVE-2026-41862 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.3% of all scored CVEs.
What is the CVSS score of CVE-2026-41862?
CVE-2026-41862 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-41862?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41862, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-41862

Explore →

Is Your Infrastructure Affected by CVE-2026-41862?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs