CVE-2026-41731

In Spring for Apache Kafka, overly broad trusted-package matching in header mappers exposes JDK classes to deserialization

HIGH
8.1
CVSS Score
Published: June 9, 2026 at 11:49 PM UTC
Updated: August 5, 2026 at 01:22 PM UTC
4 products affected across 3 vendorsFuseJBoss Enterprise Application Platform Expansion PackSpring for Apache Kafka

Using Spring for Apache Kafka by Spring?

Get instant alerts when new vulnerabilities affect Spring for Apache Kafka - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.8.0 ≤ v < 2.8.122.9.0 ≤ v < 2.9.143.2.0 ≤ v < 3.2.143.3.0 ≤ v < 3.3.15.14.0.0 ≤ v < 4.0.5.1
Affected range stops below 2.8.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.9.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.15.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement
2.8.0 ≤ v < 2.8.122.9.0 ≤ v < 2.9.143.2.0 ≤ v < 3.2.143.3.0 ≤ v < 3.3.15.14.0.0 ≤ v < 4.0.5.12.8.02.9.03.2.03.3.04.0.0
Affected range stops below 2.8.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.9.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.15.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.0.5.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-41731
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-41731
Issue TrackingThird Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2487375
Third Party Advisory
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-41731.json

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHvmware
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card