vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-41727

In Spring for Apache Kafka, forged retry topic headers subvert retry routing and backoff behavior

MEDIUM
6.5
CVSS Score
Published: June 9, 2026 at 11:49 PM UTC
Updated: July 23, 2026 at 07:32 PM UTC
2 products affected across 2 vendorsSpring for Apache KafkaSpring 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
Start FreeSign In
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Spring Kafka's retry topic infrastructure did not sufficiently validate user-controlled header values before acting on them. A producer could send a record with a crafted retry_topic-attempts header to supply an out-of-range attempt count and cause the retry topic router to misidentify where the message was in the retry sequence. 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.

Spring for Apache Kafka· VMware
95%
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
Spring For Apache Kafka· Spring
60%
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 (1)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-41727

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

6.5MEDIUMvmware
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-20

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.

Create accountSign in
Free plan, no card