CVE-2026-41732GHSA-GG69-9WWP-6JX2
In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.0.5.1, 1.2.17.1, 1.1.18, 2.0.6, 1.2.18
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Spring Spring for Apache Pulsar
From 2.0.0 · fixed in 2.0.5.1; From 1.2.0 · fixed in 1.2.17.1; From 1.1.0 · fixed in 1.1.18
- org.springframework.pulsar:spring-pulsarMaven
From 2.0.0 · fixed in 2.0.6
- org.springframework.pulsar:spring-pulsarMaven
From 1.2.0 · fixed in 1.2.18
- org.springframework.pulsar:spring-pulsarMaven
through 1.1.17