{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-114349","id":"CVE-2026-114349","title":"Apache Kafka broker denial of service in compressed record decoding","description":"When a broker decodes a compressed record batch, the per-record decoder reads a declared body size from the decompressed stream and allocates a buffer of that size before validating it against the bytes available or any configured limit. The size is attacker-controlled, and the batch CRC does not constrain it, so a small (around 90-byte), CRC-valid compressed produce request can declare a body siz","descriptionLong":"When a broker decodes a compressed record batch, the per-record decoder reads a declared body size from the decompressed stream and allocates a buffer of that size before validating it against the bytes available or any configured limit. The size is attacker-controlled, and the batch CRC does not constrain it, so a small (around 90-byte), CRC-valid compressed produce request can declare a body size of up to about 2 GiB and force the broker to attempt that allocation, raising OutOfMemoryError. The record size limit (max.message.bytes), the request size limit, and client/broker quotas bound only the compressed wire size, not the declared decompressed size.\n\n\nImpact:\n\nAn authenticated principal with Write on a topic can crash broker request-handler threads (reached when a batch's codec differs from the topic's compression.type and records are re-encoded) and any consumer that fetches the record, denying service. On brokers started with -XX:+ExitOnOutOfMemoryError, a common hardening, a single crafted request terminates the broker JVM. More seriously, a crafted record  is accepted at ingest and written to disk; when the log-cleaner later reads it on a compacted topic, the OutOfMemoryError (an Error, not an Exception) terminates the cleaner thread, which is not restarted. With the default of a single cleaner thread, log compaction then stops for the entire broker, including the internal __consumer_offsets and __transaction_state topics, and the condition persists across restarts until the offending record is removed. The impact is availability only; no data is disclosed or altered.\n\n\nMitigation:\n\nUpgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0, and set max.decompressed.message.bytes (at the broker and/or topic level) to a bounded value appropriate for your workload. Upgrading alone is not sufficient: for backward compatibility this configuration defaults to an effectively unlimited value (about 2 GiB), so a broker remains exposed until the limit is set. Choose a value at or slightly above the largest legitimate decompressed record your applications produce, and comfortably below the broker heap divided by the number of request-handler and cleaner threads. Until you can upgrade and configure the limit, restrict Write access to trusted producers; quotas and max.message.bytes do not mitigate this issue.\n\n\nResolution:\n\nFrom Apache Kafka 4.2.2, 4.3.2, and 4.4.0: the broker validates a record's declared decompressed body size against max.decompressed.message.bytes before allocating, on the produce-validation, log-compaction, and timestamp-lookup paths, and rejects oversized or negative sizes with InvalidRecordException. Operators must set this configuration to a bounded value to be protected, as its default is effectively unlimited.","published":"2026-10-28T16:46:54.920Z","updated":"2026-11-05T18:17:01.367Z","reserved":"2026-10-21T08:14:55.090Z","status":"Awaiting Analysis","rejected":false,"assigner":"apache","metric":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"CISA-ADP"},"metrics":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","rating":"medium","source":"CISA-ADP"}],"rating":"medium","products":["Apache Software Foundation Apache Kafka"],"affectedProducts":[{"vendor":"Apache Software Foundation","product":"Apache Kafka","defaultStatus":"unaffected","versions":[{"status":"affected","version":"0.11.0.0","lessThan":"2.5.0","versionType":"maven"}],"platforms":[]},{"vendor":"Apache Software Foundation","product":"Apache Kafka","defaultStatus":"unaffected","versions":[{"status":"affected","version":"0.11.0.0","lessThan":"4.0.0","versionType":"maven"}],"platforms":[]},{"vendor":"Apache Software Foundation","product":"Apache Kafka","defaultStatus":"unaffected","versions":[{"status":"affected","version":"2.4.0","lessThanOrEqual":"4.1.2","versionType":"maven"},{"status":"affected","version":"4.2.0","lessThanOrEqual":"4.2.1","versionType":"maven"},{"status":"affected","version":"4.3.0","lessThanOrEqual":"4.3.1","versionType":"maven"}],"platforms":[]}],"packages":[],"cwes":["CWE-789","CWE-400","CWE-1284"],"aliases":[],"references":[{"url":"https://kafka.apache.org/cve-list","tags":["vendor-advisory"]},{"url":"https://lists.apache.org/thread/hdy56hrd1h9btf30jb1noswsx32l17dq","tags":["mailing-list"]},{"url":"http://www.openwall.com/lists/oss-security/2026/10/28/18","tags":[]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"},"epss":0.00549,"epssPercentile":0.46836,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-114349","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-114349","ok":true,"note":"Awaiting Analysis"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-114349","ok":false,"note":"no open-source package data"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-114349","ok":true,"note":"scored 2026-11-20"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}