CVE-2026-41727: In Spring for Apache Kafka, forged retry topic headers subvert retry routing and backoff behavior
Spring · Spring for Apache Kafka
Vendor fix available · Affected: Spring for Apache Kafka · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 15% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Spring · Spring for Apache Kafkafrom 4.0.0 before 4.0.5.1; from 3.3.0 before 3.3.15.1; from 3.2.0 before 3.2.14; from 2.9.0 before 2.9.14; from 2.8.0 before 2.8.12
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
CoverageNo articles yet
No CyberSIXT article names CVE-2026-41727 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.