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.
Project Subscriptions
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://spring.io/security/cve-2026-41731 |
|
Wed, 10 Jun 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 10 Jun 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Spring
Spring spring For Apache Kafka Vmware Vmware spring For Apache Kafka |
|
| Vendors & Products |
Spring
Spring spring For Apache Kafka Vmware Vmware spring For Apache Kafka |
Wed, 10 Jun 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | In Spring for Apache Kafka, overly broad trusted-package matching in header mappers exposes JDK classes to deserialization | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2026-06-10T17:18:19.967Z
Reserved: 2026-04-22T06:21:39.015Z
Link: CVE-2026-41731
Updated: 2026-06-10T17:18:16.919Z
Status : Awaiting Analysis
Published: 2026-06-10T00:16:52.597
Modified: 2026-06-10T19:24:04.320
Link: CVE-2026-41731
No data.
OpenCVE Enrichment
Updated: 2026-06-10T11:21:30Z