CVE-2026-41731
Last modified
CVE-2026-41731 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. 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.. EPSS estimates a 0.51% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Vmware | Spring For Apache Kafka | >= 2.8.0, < 2.8.12 |
| Vmware | Spring For Apache Kafka | >= 2.9.0, < 2.9.14 |
| Vmware | Spring For Apache Kafka | >= 3.2.0, < 3.2.14 |
| Vmware | Spring For Apache Kafka | >= 3.3.0, < 3.3.15.1 |
| Vmware | Spring For Apache Kafka | >= 4.0.0, < 4.0.5.1 |
| Redhat | Fuse | 7.0.0 |
| Redhat | Jboss Enterprise Application Platform Expansion Pack | All versions |
References
- https://spring.io/security/cve-2026-41731Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2026-41731Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2487375Issue Tracking, Third Party Advisory
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41731.jsonThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-41731?
How severe is CVE-2026-41731?
How do I fix CVE-2026-41731?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-41726When an application opts into DelegatingDeserializer, a prod…6.5
- CVE-2026-41727Spring Kafka's retry topic infrastructure did not sufficient…6.5
- CVE-2026-41728Spring Data REST's JSON Patch (application/json-patch+json) …7.5
- CVE-2026-41729Spring Data REST is vulnerable to SpEL expression injection …8.1
- CVE-2026-4173A flaw has been found in CodePhiliaX Chat2DB up to 0.3.7. Th…6.3
- CVE-2026-41730Spring Data REST serializes the full exception cause chain i…5.3
- CVE-2026-41732JsonPulsarHeaderMapper matched type headers against trusted …8.1
- CVE-2026-4174A vulnerability has been found in Radare2 5.9.9. This issue …3.3
- CVE-2026-4175A vulnerability was determined in Aureus ERP up to 1.3.0-BET…5.1
- CVE-2026-4176Perl versions from 5.9.4 before 5.40.4-RC1, from 5.41.0 befo…9.8
- CVE-2026-4177YAML::Syck versions through 1.36 for Perl has several potent…9.1
- CVE-2026-4178Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2026-41731?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
