CVSS 3.1
9.1 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HCritical (9.1) in apache software foundation apache kafka. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Kafka | from 1.1.0 through 4.1.2 |
| Apache Software Foundation Apache Kafka | from 4.2.0 through 4.2.1 |
| Apache Software Foundation Apache Kafka | from 4.3.0 through 4.3.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | Pro:18.04:LTS | kafka | no fix listed | UBUNTU-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 rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Quarkus | kafka-streams | Fix deferred | |
| Red Hat Fuse 7 | kafka-streams | Out of support scope | |
| streams for Apache Kafka 3 | kafka-streams | Fix 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.