dbcve.org
Spring FrameworkFramework / library · VMware

CVE-2026-41855

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 5.3.49 / 6.1.28 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In an untrusted JMS environment, org.springframework.jms.support.converter.MappingJackson2MessageConverter and org.springframework.jms.support.converter.JacksonJsonMessageConverter allow arbitrary class instantiation, which can lead to unauthorized actions via gadget class deserialization. Affected versions: Spring Framework 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.

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 confidence

This is a deserialization gadget vulnerability in Spring Framework's JMS message converters. In untrusted JMS environments, MappingJackson2MessageConverter and JacksonJsonMessageConverter can be exploited to instantiate arbitrary classes via gadget chain deserialization, potentially achieving remote code execution.

MitigationUpgrade Spring Framework to patched versions beyond 7.0.7, 6.2.18, 6.1.27, or 5.3.48; if upgrade is not immediately possible, implement message filtering and avoid processing untrusted JMS messages with these converters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring FrameworkFramework / library
Affected:>= 5.3.0, < 5.3.49>= 6.1.0, < 6.1.28>= 6.2.0, < 6.2.18.1>= 7.0.0, < 7.0.7.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Spring Framework version in your application
    Check your build configuration (pom.xml, build.gradle) for the spring-core or spring-framework-bom version, or inspect the META-INF/MANIFEST.MF file inside the spring-core.jar in your runtime classpath
    Affected if The version falls within any of these ranges: 5.3.0 to 5.3.48, 6.1.0 to 6.1.27, 6.2.0 to 6.2.18, or 7.0.0 to 7.0.7.0
  2. Determine if JMS message converters are in use
    Search your codebase and configuration for references to MappingJackson2MessageConverter or JacksonJsonMessageConverter classes, typically configured in JMS listener container factories or message converter bean definitions
    Affected if Either MappingJackson2MessageConverter or JacksonJsonMessageConverter is configured as the message converter for JMS listeners
  3. Verify JMS message listener configuration
    Inspect your JMS listener bean definitions (such as @JmsListener annotations) and their associated message converter settings to see if JSON message conversion is enabled
    Affected if JMS listeners are configured with JSON-based message conversion using the affected converter classes
  4. Identify the trust boundary of incoming JMS messages
    Review your JMS connection configuration (connection factories, message brokers) and determine whether messages originate from internal trusted systems or external/untrusted sources
    Affected if The application receives JMS messages from external or untrusted JMS brokers or sources outside your trusted network

You are affected if your Spring Framework version is within the vulnerable ranges AND you use MappingJackson2MessageConverter or JacksonJsonMessageConverter to process JMS messages from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 5.3.49 / 6.1.28 / 6.2.18.1 or later
Fixed in 5.3.496.1.286.2.18.1
Interim mitigation

Upgrade Spring Framework to patched versions beyond 7.0.7, 6.2.18, 6.1.27, or 5.3.48; if upgrade is not immediately possible, implement message filtering and avoid processing untrusted JMS messages with these converters.

Recommended fix High confidence

Spring Framework 5.3.49, 6.1.28, 6.2.18.1, or 7.0.7.1 (depending on your major version line)

  1. 1. Identify which Spring Framework version is currently in use by checking your project's dependency management (e.g., pom.xml, build.gradle, or Maven/Gradle wrapper properties).
  2. 2. Determine the major version line in use (5.3.x, 6.1.x, 6.2.x, or 7.0.x).
  3. 3. For Spring Framework 5.3.x: Update to version 5.3.49 or later.
  4. 4. For Spring Framework 6.1.x: Update to version 6.1.28 or later.
  5. 5. For Spring Framework 6.2.x: Update to version 6.2.18.1 or later.
  6. 6. For Spring Framework 7.0.x: Update to version 7.0.7.1 or later.
  7. 7. If using JacksonJsonMessageConverter or MappingJackson2MessageConverter in a JMS context with untrusted input, ensure the upgrade is applied before processing any untrusted JMS messages.
  8. 8. Rebuild and test the application to verify the update does not break existing functionality.
Caveat Minor/patch updates typically have low breaking change risk; however, review Spring Framework 7.0 migration notes for any API changes if upgrading across major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41855 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41855 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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