{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-111496","assignerOrgId":"f0158376-9dc2-43b6-827c-5f631a4d8d09","state":"PUBLISHED","assignerShortName":"apache","dateReserved":"2026-10-16T09:55:02.432Z","datePublished":"2026-10-28T16:45:08.114Z","dateUpdated":"2026-10-28T20:06:55.726Z"},"containers":{"cna":{"providerMetadata":{"orgId":"f0158376-9dc2-43b6-827c-5f631a4d8d09","shortName":"apache","dateUpdated":"2026-10-28T16:45:08.114Z"},"title":"Apache Kafka: Kafka Streams StreamThread hang from integer overflow in stream-time punctuation","problemTypes":[{"descriptions":[{"description":"CWE-190 Integer overflow or wraparound","lang":"en","cweId":"CWE-190","type":"CWE"}]},{"descriptions":[{"description":"CWE-835 Loop with unreachable exit condition ('infinite loop')","lang":"en","cweId":"CWE-835","type":"CWE"}]}],"source":{"discovery":"EXTERNAL"},"affected":[{"vendor":"Apache Software Foundation","product":"Apache Kafka","packageURL":"pkg:maven/org.apache.kafka/kafka-streams","versions":[{"status":"affected","version":"1.1.0","lessThanOrEqual":"4.1.2","versionType":"semver"},{"status":"affected","version":"4.2.0","lessThanOrEqual":"4.2.1","versionType":"semver"},{"status":"affected","version":"4.3.0","lessThanOrEqual":"4.3.1","versionType":"semver"}],"defaultStatus":"unaffected","collectionURL":"https://repo.maven.apache.org/maven2","packageName":"org.apache.kafka:kafka-streams"}],"descriptions":[{"value":"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.\n\n\nImpact:\n\nA 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.\n\n\nMitigation:\n\nUpgrade 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.\n\n\nResolution:\n\nFrom 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.","lang":"en","supportingMedia":[{"type":"text/html","base64":false,"value":"<div>Kafka Streams derives its stream-time clock from record timestamps. PunctuationSchedule.next()&nbsp;<span>computed the next punctuation time as timestamp + (intervalsMissed + 1) * interval with no&nbsp;</span><span>overflow check. A record with a timestamp at or near Long.MAX_VALUE advances stream time to that&nbsp;</span><span>value, so the next stream-time punctuation overflows to a negative time. PunctuationQueue then&nbsp;</span><span>re-queues that time and loops on it indefinitely while holding a lock, stalling the StreamThread.</span></div><br><div>Impact:</div><div>A single record is enough. The affected StreamThread stops processing, and because the record&nbsp;<span>stays in the topic the hang returns on restart; an application whose partitions are all affected&nbsp;</span><span>becomes unresponsive. Only the Streams application is affected, not the brokers or the cluster.&nbsp;</span><span>Triggering it needs write access to a source topic whose topology uses stream-time punctuation,&nbsp;</span><span>and a broker that stores the record: brokers from Apache Kafka 4.0.0 reject such a timestamp by&nbsp;</span><span>default (log.message.timestamp.after.max.ms, one hour), so it is reachable only on older brokers&nbsp;</span><span>or where that bound has been relaxed.</span></div><br><div>Mitigation:</div><div>Upgrade Kafka Streams to 4.2.2, 4.3.2, or 4.4.0. As defense in depth, keep&nbsp;<span>log.message.timestamp.after.max.ms bounded on source topics and restrict write access to them.</span></div><br><div>Resolution:</div><div>From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: the next punctuation time is computed with&nbsp;<span>overflow-checked arithmetic (clamped to Long.MAX_VALUE), and a rescheduled punctuation is&nbsp;</span><span>re-queued only when its time moves forward.</span></div>"}]}],"references":[{"url":"https://kafka.apache.org/cve-list","tags":["vendor-advisory"]}],"metrics":[{"other":{"type":"Textual description of severity","content":{"text":"low"}},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"credits":[{"lang":"en","value":"Mike Read (GitHub: Michael-JRead)","type":"reporter"},{"lang":"en","value":"Matthias J. Sax <matthias@confluent.io>","type":"remediation developer"}],"x_generator":{"engine":"Vulnogram 1.0.3"}},"adp":[{"title":"CVE Program Container","references":[{"url":"http://www.openwall.com/lists/oss-security/2026/10/28/14"}],"providerMetadata":{"orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE","dateUpdated":"2026-10-28T20:06:55.726Z"}}]}}