CVE-2026-41727 json
In Spring for Apache Kafka, forged retry topic headers subvert retry routing and backoff behavior
published 2026-06-09 5 mo ago modified 2026-08-12 2 mo ago also GHSA-53w6-v7cv-fc9h , EUVD-2026-35904
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.kafka:spring-kafka 3.3.16, 4.0.6
- Spring Spring for Apache Kafka 2.8.12, 2.9.14, 3.2.14, 3.3.15.1, 4.0.5.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.kafka:spring-kafka | >=4.0.0, <4.0.6 >=3.3.0, <3.3.16 >=3.2.0, <=3.2.13 >=2.9.0, <=2.9.13 <=2.8.11 |
4.0.6 3.3.16 |
Affected products
- Spring Spring for Apache Kafka
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- CVE List CVE-2026-41727
- GitHub Advisory GHSA-53w6-v7cv-fc9h
- NVD CVE-2026-41727
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.