CVE-2026-59317

In Spring for Apache Kafka, missing header validation in DeadLetterPublishingRecovererFactory enables denial of service via a poison-pill loop

Published Aug 27, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
DeadLetterPublishingRecovererFactory reads the retry_topic-original-timestamp header from an inbound ConsumerRecord and passes its raw bytes directly to new BigInteger(header.value()) with no length or format validation.
Spring for Apache Kafka 4.1.0
Spring for Apache Kafka 4.0.0 - 4.0.6
Spring for Apache Kafka 3.0.0 - 3.3.16
Spring for Apache Kafka 2.9.0 - 2.9.14
Spring for Apache Kafka 2.8.12 and earlier

Analysis

AI-generated

Technical impact

A header value supplied by an inbound consumer record is parsed directly into a BigInteger without any validation on length or format. This flaw can cause an application to enter an uncontrolled retry loop, consuming CPU and memory resources and potentially exhausting them, resulting in denial of service. The weakness lies in improper input validation during message processing.

Affected Systems

The affected products are Spring for Apache Kafka releases 4.1.0 and 4.0.0 through 4.0.6, 3.0.0 through 3.3.16, 2.9.0 through 2.9.14, and all 2.8.12 versions and earlier.

Risk and Exploitability

The CVSS score of 6.5 indicates a moderate severity. The EPSS score is 0.00367, indicating a low probability of exploitation, and the vulnerability is not listed in the KEV catalog. Attackers can exploit the flaw by crafting a message with a malicious "retry_topic-original-timestamp" header and sending it to a consumer instance that uses DeadLetterPublishingRecovererFactory. Based on the description, the likely attack vector is through network access that allows message production to the Kafka broker used by the vulnerable consumer.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring for Apache Kafka to the latest release that includes the header validation fix.
  • If an upgrade cannot be performed immediately, configure message producers to limit the length and format of the "retry_topic-original-timestamp" header before it reaches the consumer.
  • Configure the consumer to temporarily disable DeadLetterPublishingRecovererFactory or replace it with a custom implementation that validates the header before conversion.

Generated by OpenCVE AI on August 29, 2026 at 02:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring For Apache Kafka
CPEs cpe:2.3:a:vmware:spring_for_apache_kafka:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring For Apache Kafka
Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
Weaknesses CWE-1284
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring For Apache Kafka
Vendors & Products Spring
Spring spring For Apache Kafka
Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
Description DeadLetterPublishingRecovererFactory reads the retry_topic-original-timestamp header from an inbound ConsumerRecord and passes its raw bytes directly to new BigInteger(header.value()) with no length or format validation. Spring for Apache Kafka 4.1.0 Spring for Apache Kafka 4.0.0 - 4.0.6 Spring for Apache Kafka 3.0.0 - 3.3.16 Spring for Apache Kafka 2.9.0 - 2.9.14 Spring for Apache Kafka 2.8.12 and earlier
Title In Spring for Apache Kafka, missing header validation in DeadLetterPublishingRecovererFactory enables denial of service via a poison-pill loop
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-1284

    Improper Validation of Specified Quantity in Input

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 10:47 PM
Reserved
Jul 4, 2026, 6:13 PM
Status
Analyzed
Published
Aug 27, 2026, 8:17 PM
Modified
Sep 4, 2026, 7:21 PM