Deserialization in Spring For Apache Pulsar

CVE-2026-41732

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.004 (35.4th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 35th percentile — 35.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-41732: held from 0.003 to 0.004.

EPSS over last 30 days · oldest: 0.003 · newest: 0.004 · change: +0.001

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-41732?
CVE-2026-41732 is a high-severity vulnerability in Spring For Apache Pulsar, classified under Deserialization of Untrusted Data. CVSS score: 8.1/10. Published 2026-06-10.
How severe is CVE-2026-41732?
High severity. CVSS v3 base score is 8.1 out of 10.