Unsafe Deserialization in org.springframework:spring-jms (CVE-2026-41855)
Summary
Vulnerability in org.springframework:spring-jms (CVE-2026-41855). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 7.0.8 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41855 has been found in org.springframework:spring-jms.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade org.springframework:spring-jms to 7.0.8 or later.
If unsure, ask your IT team or search "org.springframework:spring-jms CVE-2026-41855" on the vendor's site.
CVE-2026-41855 (org.springframework:spring-jms) — CWE-502 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 7.0.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in org.springframework:spring-jms.
Check the vendor advisory for the affected versions of org.springframework:spring-jms.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 7.0.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springframework:spring-jms を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springframework:spring-jms to 7.0.8ステージング環境で 7.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-41855 libspring-java
- Ubuntu UBUNTU-CVE-2026-41855 libspring-java
References
- advisory nvd.nist.gov
- package github.com
- web spring.io
- web github.com
- web github.com