CVE-2026-41732 json
In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization
published 4mo ago modified 2mo ago also GHSA-gg69-9wwp-6jx2 , EUVD-2026-35909
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.pulsar:spring-pulsar 1.2.18, 2.0.6
- Spring Spring for Apache Pulsar 1.1.18, 1.2.17.1, 2.0.5.1
Is CVE-2026-41732 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.pulsar:spring-pulsar | >=2.0.0, <2.0.6 >=1.2.0, <1.2.18 <=1.1.17 |
2.0.6 1.2.18 |
Affected products
- Spring Spring for Apache Pulsar
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
Sources
- CVE List CVE-2026-41732
- GitHub Advisory GHSA-gg69-9wwp-6jx2
- NVD CVE-2026-41732
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.