CVE-2026-41732: CWE-502: Deserialization of Untrusted Data in Spring Spring for Apache Pulsar
JsonPulsarHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Additionally, an empty trusted-packages configuration fell back to trusting all packages rather than applying a safe default allow-list. Affected versions: Spring for Apache Pulsar 2.0.0 through 2.0.5; 1.2.0 through 1.2.17; 1.1.0 through 1.1.17.
AI Analysis
Technical Summary
The vulnerability in Spring for Apache Pulsar involves the JsonPulsarHeaderMapper's method of validating trusted packages by prefix matching, which causes implicit trust of all subpackages under any trusted package. Furthermore, an empty trusted-packages configuration results in trusting all packages by default instead of applying a restrictive allow-list. This behavior enables deserialization of untrusted data, classified under CWE-502, potentially allowing attackers to execute arbitrary code or cause denial of service. Affected versions include 1.1.0 through 1.1.17, 1.2.0 through 1.2.17, and 2.0.0 through 2.0.5 of Spring for Apache Pulsar. The CVSS v3.1 score is 8.1, indicating high severity with network attack vector, high impact on confidentiality, integrity, and availability, and no required privileges or user interaction. No vendor advisory or patch information is currently available.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker to perform unsafe deserialization of untrusted data, potentially leading to remote code execution, data compromise, or denial of service. The vulnerability affects confidentiality, integrity, and availability of the affected system. No known exploits in the wild have been reported yet.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid using empty trusted-packages configurations and carefully restrict trusted packages to minimize exposure. Monitor vendor channels for updates and apply patches promptly once available.
CVE-2026-41732: CWE-502: Deserialization of Untrusted Data in Spring Spring for Apache Pulsar
Description
JsonPulsarHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Additionally, an empty trusted-packages configuration fell back to trusting all packages rather than applying a safe default allow-list. Affected versions: Spring for Apache Pulsar 2.0.0 through 2.0.5; 1.2.0 through 1.2.17; 1.1.0 through 1.1.17.
CVSS v3.1
Score 8.1high
Affected software
pkg:maven/org.springframework/spring-for-apache-pulsarRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Spring for Apache Pulsar involves the JsonPulsarHeaderMapper's method of validating trusted packages by prefix matching, which causes implicit trust of all subpackages under any trusted package. Furthermore, an empty trusted-packages configuration results in trusting all packages by default instead of applying a restrictive allow-list. This behavior enables deserialization of untrusted data, classified under CWE-502, potentially allowing attackers to execute arbitrary code or cause denial of service. Affected versions include 1.1.0 through 1.1.17, 1.2.0 through 1.2.17, and 2.0.0 through 2.0.5 of Spring for Apache Pulsar. The CVSS v3.1 score is 8.1, indicating high severity with network attack vector, high impact on confidentiality, integrity, and availability, and no required privileges or user interaction. No vendor advisory or patch information is currently available.
Potential Impact
Successful exploitation of this vulnerability could allow an attacker to perform unsafe deserialization of untrusted data, potentially leading to remote code execution, data compromise, or denial of service. The vulnerability affects confidentiality, integrity, and availability of the affected system. No known exploits in the wild have been reported yet.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid using empty trusted-packages configurations and carefully restrict trusted packages to minimize exposure. Monitor vendor channels for updates and apply patches promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- vmware
- Date Reserved
- 2026-04-22T06:21:39.015Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a28a8098dd33fbd8595f117
Added to database: 06/09/2026, 23:55:53 UTC
Last enriched: 06/28/2026, 21:01:05 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 117
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.