CVE-2026-41732
Header trust bypass in JsonPulsarHeaderMapper; empty trusted-packages trusts all.
Is CVE-2026-41732 being exploited?
Not confirmed. CVE-2026-41732 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-41732?
CVE-2026-41732 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41732?
Yes. A fix has been recorded for CVE-2026-41732. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41732 affect?
CVE-2026-41732 affects Spring for Apache Pulsar 2.0.0-2.0.5, Spring for Apache Pulsar 1.2.0-1.2.17, Spring for Apache Pulsar 1.1.0-1.1.17. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41732?
Upgrade to fixed release; review trusted-packages configuration
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can force loading of subtypes via crafted headers; empty trusted-packages trusts all packages, enabling potential RCE.
Patch when possible
- affected>= 2.0.0 and < 2.0.5.1
- affected>= 1.2.0 and < 1.2.17.1
- affected>= 1.1.0 and < 1.1.18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.