published 9 Jun 2026 · updated 27 Jun 2026
In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization
8.1HighCVSS 8.1EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.1.18, 1.2.17.1 and 2.0.5.1.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Spring | >=1.1.0 <1.1.18, >=1.2.0 <1.2.17.1, >=2.0.0 <2.0.5.1 | 1.1.18, 1.2.17.1, 2.0.5.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket