Medium [CVE-2026-41727] Spring Kafka's retry topic infrastructure did not sufficiently validate user-controlled header values before acting on them
This medium-severity VMware (Broadcom) advisory covers CVE-2026-41727.
Android app · Google Play
Monitor future VMware (Broadcom) CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
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.
- 4.0.0
- 4.0.5
- 3.3.0
- 3.3.15
- 3.2.0
- 3.2.13
- 2.9.0
- 2.9.13
- 2.8.0
- 2.8.11
NVD record · high-confidence parse· fetched 2 months ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
NVD record · high-confidence parse· fetched 2 months ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
NVD record · high-confidence parse· fetched 2 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.