cve.bz

CVE-2026-111496 apache software foundation apache kafka: Year 2038 problem, Y2K38, Y2038, Epochalypse

9.1 criticalEPSS 0.5%

Critical (9.1) in apache software foundation apache kafka. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-111496 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111496?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111496?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111496 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache kafka

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kafkafrom 1.1.0 through 4.1.2
Apache Software Foundation Apache Kafkafrom 4.2.0 through 4.2.1
Apache Software Foundation Apache Kafkafrom 4.3.0 through 4.3.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
UbuntuPro:18.04:LTSkafkano fix listedUBUNTU-CVE-2026-111496

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because exploitation requires authenticated write permissions to a source topic feeding a stream-time punctuation topology, and affects only client-side stream processing threads rather than the core Kafka broker infrastructure. Furthermore, brokers configured with default timestamp boundary checks reject extreme future timestamps, limiting practical exploitability to environments where timestamp validation is disabled or relaxed. If triggered, the flaw results in stream processing thread deadlocks, halting partition consumption until the malformed message is handled.

Red Hat's mitigation

To reduce exposure to this issue without modifying application binaries:

1. Restrict write access to source topics:

Enforce Kafka Access Control Lists (ACLs) to restrict write permissions on topics consumed by Kafka Streams topologies that rely on stream-time punctuation, ensuring only authorized producers can publish records.

2. Enforce timestamp boundaries on brokers and topics:

Configure timestamp limits on Kafka source topics to reject messages with extreme future timestamps. Apply the topic configuration dynamically using administrative scripts:

kafka-configs.sh --bootstrap-server <broker-host>:<port> --entity-type topics --entity-name <topic-name> --alter --add-config log.message.timestamp.after.max.ms=3600000

Alternatively, enforce `log.message.timestamp.after.max.ms` cluster-wide in the broker configuration file.

Caveats:

Restricting message timestamp boundaries causes brokers to reject records outside the configured time delta, which could disrupt producers with unsynchronized system clocks. If applying changes cluster-wide at the broker configuration level, a service restart or configuration reload of Kafka brokers is required, which may temporarily disrupt active client connections.

ProductPackageStateAdvisory
Red Hat build of Quarkuskafka-streamsFix deferred
Red Hat Fuse 7kafka-streamsOut of support scope
streams for Apache Kafka 3kafka-streamsFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111496.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON