CVE-2026-41727: Spring for Apache Kafka · Improper Input Validation
Affects Spring for Apache KafkaSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 4.0.5.1 : update Spring for Apache Kafka when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.5.1, 3.3.15.1, 3.2.14 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SpringSpring for Apache Kafka | Affected
| Fixed in
|
| SpringSpring for Apache Kafka | Affected
| Fixed in
|
| SpringSpring for Apache Kafka | Affected
| Fixed in
|
| SpringSpring for Apache Kafka | Affected
| Fixed in
|
| SpringSpring for Apache Kafka | Affected
| Fixed in
|
Mavenorg.springframework.kafka/spring-kafkapkg:maven/org.springframework.kafka/spring-kafkaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should consider restricting producer access to trusted sources to prevent malicious header manipulation.
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.