How severe is CVE-2026-41731?

CVE-2026-41731 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-41731 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-41731?

CVE-2026-41731 primarily affects Vmware Spring For Apache Kafka. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2026-41731?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-41731 have an EU (EUVD) identifier?

Yes. CVE-2026-41731 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35908.

When was CVE-2026-41731 published?

CVE-2026-41731 was published on 2026-06-10 and last updated on 2026-08-05.

CVE-2026-41731

CVE-2026-41731 is a high-severity vulnerability in Vmware Spring For Apache Kafka with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-502.

Key facts

Severity: High (CVSS 3.x base score 8.1)
EPSS exploit prediction: 1% (41st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-35908
Weakness: CWE-502
Affected product: Vmware Spring For Apache Kafka
Published: 2026-06-10
Last modified: 2026-08-05

Description

JsonKafkaHeaderMapper and the deprecated DefaultKafkaHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Combined with Jackson's default bean deserialization, a producer could supply crafted header values that caused the consumer to deserialize arbitrary JDK types. Affected versions: Spring for Apache Kafka 4.0.0 through 4.0.5; 3.3.0 through 3.3.15; 3.2.0 through 3.2.13; 2.9.0 through 2.9.13; 2.8.0 through 2.8.11.

Frequently asked questions

What is CVE-2026-41731?: JsonKafkaHeaderMapper and the deprecated DefaultKafkaHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Combined with Jackson's default bean deserialization, a producer could supply crafted header values that caused the consumer to deserialize arbitrary JDK types. Affected versions: Spring for Apache Kafka 4.0.0 through 4.0.5; 3.3.0 through 3.3.15; 3.2.0 through 3.2.13; 2.9.0 through 2.9.13; 2.8.0 through 2.8.11.
How severe is CVE-2026-41731?: CVE-2026-41731 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-41731 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41731?: CVE-2026-41731 primarily affects Vmware Spring For Apache Kafka. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-41731?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-41731 have an EU (EUVD) identifier?: Yes. CVE-2026-41731 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-35908.
When was CVE-2026-41731 published?: CVE-2026-41731 was published on 2026-06-10 and last updated on 2026-08-05.

References

Affected products (3)

cpe:2.3:a:vmware:spring_for_apache_kafka:*:*:*:*:*:*:*:*
cpe:2.3:a:redhat:fuse:7.0.0:*:*:*:*:*:*:*
cpe:2.3:a:redhat:jboss_enterprise_application_platform_expansion_pack:-:*:*:*:*:*:*:*

More vulnerabilities in Vmware Spring For Apache Kafka

CVE-2026-41727 — Medium (CVSS 6.5): Spring Kafka's retry topic infrastructure did not sufficiently validate user-controlled header values before acting on…
CVE-2026-41726 — Medium (CVSS 6.5): When an application opts into DelegatingDeserializer, a producer can grow the consumer's heap without bound by sending…
CVE-2023-34040 — Medium (CVSS 5.3): In Spring for Apache Kafka 3.0.9 and earlier and versions 2.9.10 and earlier, a possible deserialization attack vector…

All CVEs affecting Vmware Spring For Apache Kafka →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

CVE-2026-69836 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Entra ID allows an unauthorized attacker to execute code over a network.
CVE-2026-17061 — Critical (CVSS 10.0): A Deserialization of Untrusted Data vulnerability affecting SIMULIA Execution Engine from Release 2023 through Release…
CVE-2026-11756 — Critical (CVSS 10.0): A Deserialization of Untrusted Data vulnerability affecting Station Launcher App in 3DEXPERIENCE platform from Release…
CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →