CVE-2026-41732: JsonPulsarHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusti

This month

HIGH 8.1REMOTEWATCHLISTUPGRADE

CVE-2026-41732 is a high-severity flaw (CVSS 8.1) affecting spring for apache pulsar. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-06-10
Last modified	2026-07-23

Publisher (CNA): VMware · Vendor: vmware

Last updated 2026-07-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-10 00:16 UTCPublished CVE record published
2026-07-23 09:10 UTCUpdated Record last modified

vmware spring for apache pulsar UPGRADE

Affected: >= 1.1.0 and < 1.1.18 · >= 1.2.0 and < 1.2.17.1 · >= 2.0.0 and < 2.0.6

Fixed in: 1.1.18, 1.2.17.1, 2.0.6

Safe to downgrade to: a release before 1.1.0

1. Check installed version

apt-cache policy spring-for-apache-pulsar || rpm -q spring-for-apache-pulsar || spring-for-apache-pulsar --version

2. UPGRADE to 1.1.18 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-for-apache-pulsar

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-for-apache-pulsar

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.1.0 (Debian / Ubuntu)

apt-cache madison spring-for-apache-pulsar sudo apt install spring-for-apache-pulsar=<VERSION_BEFORE_1.1.0> sudo apt-mark hold spring-for-apache-pulsar

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-for-apache-pulsar sudo dnf downgrade spring-for-apache-pulsar-<VERSION_BEFORE_1.1.0> sudo dnf versionlock add spring-for-apache-pulsar

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41732?

spring for apache pulsar: upgrade to 1.1.18, 1.2.17.1, 2.0.6. Exact commands for each OS are on this page.

Is CVE-2026-41732 being exploited?

CVE-2026-41732 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41732 affect?

CVE-2026-41732 affects spring for apache pulsar. Severity is high (CVSS 8.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 trust

How urgent is CVE-2026-41732?

Priority 45/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

VMware vulnerabilities

References

← Back to latest CVEs