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.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://spring.io/security/cve-2026-41727 |
|
History
Wed, 10 Jun 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | In Spring for Apache Kafka, forged retry topic headers subvert retry routing and backoff behavior | |
| Weaknesses | CWE-20 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2026-06-09T23:49:10.215Z
Reserved: 2026-04-22T06:21:39.014Z
Link: CVE-2026-41727
No data.
Status : Received
Published: 2026-06-10T00:16:52.143
Modified: 2026-06-10T00:16:52.143
Link: CVE-2026-41727
No data.
OpenCVE Enrichment
Updated: 2026-06-10T01:30:18Z