CVE-2026-41731 is an unsafe deserialization vulnerability in Spring for Apache Kafka's JsonKafkaHeaderMapper and deprecated DefaultKafkaHeaderMapper. The mappers used prefix-based matching for trusted packages, causing a configured trusted package to implicitly trust all subordinate package namespaces. In conjunction with Jackson default bean deserialization, crafted Kafka type-header values from a producer can cause a consuming application to deserialize arbitrary JDK types. Affected versions are 4.0.0–4.0.5, 3.3.0–3.3.15, 3.2.0–3.2.13, 2.9.0–2.9.13, and 2.8.0–2.8.11.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An input validation defect in messaging components affecting header configuration handling, enabling arbitrary class execution through crafted headers.
A deserialization-related vulnerability in Spring for Apache Kafka where trusted package checks used a prefix match in JsonKafkaHeaderMapper and DefaultKafkaHeaderMapper, allowing crafted header values to trigger deserialization of arbitrary JDK types.
A high-severity deserialization vulnerability in Spring for Apache Kafka caused by overly broad trusted-package matching in JsonKafkaHeaderMapper and DefaultKafkaHeaderMapper, allowing crafted headers to trigger deserialization of arbitrary JDK types with potentially dangerous side effects.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.