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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://spring.io/security/cve-2026-41732 |
|
Wed, 10 Jun 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 10 Jun 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Spring
Spring spring For Apache Pulsar |
|
| Vendors & Products |
Spring
Spring spring For Apache Pulsar |
Wed, 10 Jun 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2026-06-27T21:17:35.895Z
Reserved: 2026-04-22T06:21:39.015Z
Link: CVE-2026-41732
Updated: 2026-06-10T18:52:39.995Z
Status : Awaiting Analysis
Published: 2026-06-10T00:16:52.720
Modified: 2026-06-10T19:24:04.320
Link: CVE-2026-41732
No data.
OpenCVE Enrichment
Updated: 2026-06-10T11:21:29Z