CVE-2026-111496

Apache Kafka: Kafka Streams StreamThread hang from integer overflow in stream-time punctuation

Published Oct 28, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Kafka Streams derives its stream-time clock from record timestamps. PunctuationSchedule.next() computed the next punctuation time as timestamp + (intervalsMissed + 1) * interval with no overflow check. A record with a timestamp at or near Long.MAX_VALUE advances stream time to that value, so the next stream-time punctuation overflows to a negative time. PunctuationQueue then re-queues that time and loops on it indefinitely while holding a lock, stalling the StreamThread.


Impact:

A single record is enough. The affected StreamThread stops processing, and because the record stays in the topic the hang returns on restart; an application whose partitions are all affected becomes unresponsive. Only the Streams application is affected, not the brokers or the cluster. Triggering it needs write access to a source topic whose topology uses stream-time punctuation, and a broker that stores the record: brokers from Apache Kafka 4.0.0 reject such a timestamp by default (log.message.timestamp.after.max.ms, one hour), so it is reachable only on older brokers or where that bound has been relaxed.


Mitigation:

Upgrade Kafka Streams to 4.2.2, 4.3.2, or 4.4.0. As defense in depth, keep log.message.timestamp.after.max.ms bounded on source topics and restrict write access to them.


Resolution:

From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: the next punctuation time is computed with overflow-checked arithmetic (clamped to Long.MAX_VALUE), and a rescheduled punctuation is re-queued only when its time moves forward.

Analysis

AI-generated

Technical impact

Kafka Streams computes the next punctuation time as the record timestamp plus a multiple of the punctuation interval without checking for overflow. A record whose timestamp is close to Long.MAX_VALUE causes the next punctuation time to wrap to a negative value. The punctuation queue then repeatedly re-queues that negative time while holding a lock, blocking the StreamThread indefinitely. The effect is a complete halt in processing for the affected StreamThread and any application partitions that rely on it, but it does not impact Kafka brokers or the cluster overall.

Affected Systems

The vulnerability affects Apache Kafka Streams libraries prior to versions 4.2.2, 4.3.2, and 4.4.0. It is triggered by writing a single record with a timestamp near Long.MAX_VALUE to a source topic whose stream topology uses stream-time punctuation. Brokers running Apache Kafka older than version 4.0.0 accept such timestamps unless the log.message.timestamp.after.max.ms setting is tightened; newer brokers reject the value by default, limiting exploitation to older or misconfigured installations.

Risk and Exploitability

Because the exploit requires only write access to a source topic and no elevated privileges, the attack vector is straightforward. The EPSS score is less than 1%, and the CVE is not listed in the CISA KEV catalog, indicating that large‑scale exploitation has not been observed. The CVSS score of 9.1 denotes high severity, but the total loss of availability for the affected Streams application makes the risk significant, especially in environments that still use older Kafka clusters or have relaxed timestamp bounds.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Kafka Streams to 4.2.2, 4.3.2, or 4.4.0, where the next punctuation time is calculated with overflow-checked arithmetic and negative reschedule attempts are discarded.
  • Configure source topics to enforce the log.message.timestamp.after.max.ms property so that timestamps near Long.MAX_VALUE are rejected before they reach the Streams application.
  • Restrict write access to source topics that are part of stream-time punctuated topologies to limit the ability of attackers to inject malicious timestamps.

Generated by OpenCVE AI on November 5, 2026 at 21:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Metrics cvssV3_1

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

cvssV3_1

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

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Apache
Apache kafka
Vendors & Products Apache
Apache kafka
Type Values Removed Values Added
Description Kafka Streams derives its stream-time clock from record timestamps. PunctuationSchedule.next() computed the next punctuation time as timestamp + (intervalsMissed + 1) * interval with no overflow check. A record with a timestamp at or near Long.MAX_VALUE advances stream time to that value, so the next stream-time punctuation overflows to a negative time. PunctuationQueue then re-queues that time and loops on it indefinitely while holding a lock, stalling the StreamThread. Impact: A single record is enough. The affected StreamThread stops processing, and because the record stays in the topic the hang returns on restart; an application whose partitions are all affected becomes unresponsive. Only the Streams application is affected, not the brokers or the cluster. Triggering it needs write access to a source topic whose topology uses stream-time punctuation, and a broker that stores the record: brokers from Apache Kafka 4.0.0 reject such a timestamp by default (log.message.timestamp.after.max.ms, one hour), so it is reachable only on older brokers or where that bound has been relaxed. Mitigation: Upgrade Kafka Streams to 4.2.2, 4.3.2, or 4.4.0. As defense in depth, keep log.message.timestamp.after.max.ms bounded on source topics and restrict write access to them. Resolution: From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: the next punctuation time is computed with overflow-checked arithmetic (clamped to Long.MAX_VALUE), and a rescheduled punctuation is re-queued only when its time moves forward.
Title Apache Kafka: Kafka Streams StreamThread hang from integer overflow in stream-time punctuation
Weaknesses CWE-190
CWE-835
References
Weaknesses
  • CWE-190

    Integer Overflow or Wraparound

  • CWE-835

    Loop with Unreachable Exit Condition ('Infinite Loop')

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 5, 2026, 7:19 PM
Reserved
Oct 16, 2026, 9:55 AM
Status
Awaiting Analysis
Published
Oct 28, 2026, 5:17 PM
Modified
Nov 5, 2026, 8:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 4:45 PM