Skip to content
major vulnerability· requires attention

Affects widely-used Spring Framework; deserialization gadget in JMS could enable remote actions, impacting many Java apps.

Web

CVE-2026-41855

8.1
High
EPSS 0.29%Patch availableJun 9, 2026

JMS deserialization gadget in Spring allows unauthorized actions.

common questions

Is CVE-2026-41855 being exploited?

Not confirmed. CVE-2026-41855 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-41855?

CVE-2026-41855 is rated High with a CVSS score of 8.1. 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-41855?

Yes. A fix has been recorded for CVE-2026-41855. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-41855 affect?

CVE-2026-41855 affects Spring Framework 5.3.0-5.3.48, Spring Framework 6.1.0-6.1.27, Spring Framework 6.2.0-6.2.18, Spring Framework 7.0.0-7.0.7. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-41855?

Upgrade to fixed Spring Framework versions per vendor guidance

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Spring Framework 5.3.0-5.3.48Spring Framework 6.1.0-6.1.27Spring Framework 6.2.0-6.2.18Spring Framework 7.0.0-7.0.7
impact

Remote code execution via gadget deserialization in JMS converters in untrusted JMS environments.

action required

Patch when possible

affected versions
Spring Spring Framework
  • affected>= 7.0.0 and < 7.0.7.1
  • affected>= 6.2.0 and < 6.2.18.1
  • affected>= 6.1.0 and < 6.1.28
  • affected>= 5.3.0 and < 5.3.49

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free