CVE-2026-41855: VMware Spring Framework deserialization in JMS message converters

CVE-2026-41855 · Severity: high · CVSS 8.1 · Published 2026-06-09

Spring Framework's JMS message converters (MappingJackson2MessageConverter and JacksonJsonMessageConverter) deserve can instantiate arbitrary Java classes when processing messages from untrusted JMS brokers. An attacker with access to a JMS queue or topic can craft malicious messages to execute arbitrary code on the application server, potentially compromising confidentiality, integrity, and availability of the affected system.

Technologies: VMware Spring Framework. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-41855 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41855 being exploited in the wild.
How severe is CVE-2026-41855?
High severity, with a CVSS score of 8.1, published 9 June 2026.
Which products and versions are affected?
org.springframework:spring-jms (Maven) ECOSYSTEM:introduced=0,last_affected=5.3.39; VMware Spring Framework 5.3.0 through 5.3.48, 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
Is there a fix for CVE-2026-41855?
A patch was published on 2026-06-09: Patches released for Spring Framework 6.2.19 and 7.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41855 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-41855?
Check whether you run org.springframework:spring-jms (Maven) or VMware Spring Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This vulnerability is a deserialization flaw (CWE-502) in Spring Framework's Jackson-based JMS message converters. When MappingJackson2MessageConverter or JacksonJsonMessageConverter processes JMS messages in an untrusted environment, they deserialize arbitrary class types without proper validation, allowing an attacker to instantiate gadget chain classes and achieve remote code execution. The attack requires network access to the JMS broker or the ability to send messages to affected queues/topics; no authentication or user interaction is required on the application side. The vulnerability affects Spring Framework versions 5.3.0–5.3.48, 6.1.0–6.1.27, 6.2.0–6.2.18, and 7.0.0–7.0.7. Patches are available in versions 6.2.19 and 7.0.8, though earlier versions (5.3.x and 6.1.x) do not have published patch versions in the advisory data.

Affected products

  • Spring Spring Framework 5.3.0 through 5.3.48
  • Spring Spring Framework 6.1.0 through 6.1.27
  • Spring Spring Framework 6.2.0 through 6.2.18
  • Spring Spring Framework 7.0.0 through 7.0.7

Identifiers

  • CVE-2026-41855
  • GHSA-x863-p983-p4f7

Timeline

  • 2026-06-09: disclosed: Vulnerability published to GitHub Advisory Database
  • 2026-06-09: patched: Patches released for Spring Framework 6.2.19 and 7.0.8

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.