CVE-2026-41732 — spring-pulsar
HIGHCVE-2026-41732 is a high-severity (CVSS 8.1) Deserialization of Untrusted Data vulnerability in org.springframework.pulsar:spring-pulsar. A fix is available for org.springframework.pulsar:spring-pulsar — see the affected versions and patch details below.
In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41732.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.pulsar:spring-pulsar☕org.springframework.pulsar:spring-pulsar☕org.springframework.pulsar:spring-pulsarReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.pulsar:spring-pulsar | ≥ 2.0.0&&< 2.0.6 | 2.0.6org.springframework.pulsar:spring-pulsar:2.0.6 |
| ☕Maven | org.springframework.pulsar:spring-pulsar | ≥ 1.2.0&&< 1.2.18 | 1.2.18org.springframework.pulsar:spring-pulsar:1.2.18 |
| ☕Maven | org.springframework.pulsar:spring-pulsar | all versions | No fix |
Affected Products
spring for apache pulsarvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.pulsar:spring-pulsar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.pulsar:spring-pulsar to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41732 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Frequently Asked Questions
Is CVE-2026-41732 in your dependencies?
Find it across Maven, including transitive dependencies.