6.5
Moyenne
CVE-2026-41727 Spring Kafka's retry topic infrastructure did not sufficiently validate user-controlled header values before acting on…
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.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Spring For Apache Kafka 4.0 | 4.0.0 → < 4.0.5.1 | 4.0.5.1 |
| Spring For Apache Kafka 3.3 | 3.3.0 → < 3.3.15.1 | 3.3.15.1 |
| Spring For Apache Kafka 3.2 | 3.2.0 → < 3.2.14 | 3.2.14 |
| Spring For Apache Kafka 2.9 | 2.9.0 → < 2.9.14 | 2.9.14 |
| Spring For Apache Kafka 2.8 | 2.8.0 → < 2.8.12 | 2.8.12 |
Références
- spring.io spring.io
Chronologie
- Publiée
- Dernière modification
Autres CVE de Spring For Apache Kafka
Les 6 CVE de Spring For Apache Kafka →
CVE-2026-59317
DeadLetterPublishingRecovererFactory reads the retry_topic-original-timestamp header from an inbound ConsumerRecord…
6.5
Moyenne
CVE-2026-59278
JsonKafkaHeaderMapper and DefaultKafkaHeaderMapper include java.net in their default trusted packages list
6.5
Moyenne
CVE-2026-41731
JsonKafkaHeaderMapper and the deprecated DefaultKafkaHeaderMapper matched type headers against trusted packages using…
8.1
Élevée
CVE-2026-41726
When an application opts into DelegatingDeserializer, a producer can grow the consumer's heap without bound by sending…
6.5
Moyenne