CVE Professor
›
Back
CVE-2026-114349

CVE-2026-114349 — CWE-400 · CWE-789

MEDIUM CVSS 6.5 NVD

CVE-2026-114349 is a MEDIUM severity Denial-of-Service (DoS) vulnerability (CWE-400, CWE-789) (CVSS 6.5/10) affecting affected software system. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), causing high-impact service disruption (A:H).

📄 Official NVD / MITRE Original Record Text

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. Impact: An 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. Mitigation: Upgrade 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. Resolution: From 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 28.10.2026
ISO Date 2026-10-28
CVSS Version v3.1
Source NVD
CVSS v3.1 Vector Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Network AV:N
Attack Complexity Low AC:L
Privileges Req. Low PR:L
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality None C:N
Integrity None I:N
Availability High A:H
AI Security Analysis & Remediation
🤖 Generating Deep AI Security Analysis…
Analyzing CVSS vector & CWE weakness structure…

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-114349
CVSS 6.5/10 · MEDIUM · 28.10.2026
CWE: CWE-400, CWE-789
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 WHAT IS THIS VULNERABILITY?
Summary: 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 b…

⚡ ATTACK CHAIN
Remotely over internet | low-privilege account | no user interaction | low complexity.

🌍 REAL WORLD IMPACT
Service can be completely taken down.

🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add WAF rule, create IDS alert for anomalous traffic.

⚠️ URGENCY
📋 Routine update cycle (30 days)

────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]

Target Reconnaissance Queries (FOFA & Shodan)
CVSS Score
6.5 / 10 · CVSS MEDIUM
Weakness Types (CWE)
CWE-400 CWE-789 CWE-1284
References & Advisories (3)
Related CVEs
8.7
CVE-2026-130686
vLLM from 0.6.0 before 0.33.0 lacks a request-wide media budget, allowing remote inference clients to exhaust
7.5
CVE-2026-59975
SharpIppNext is a .NET Standard library for building Internet Printing Protocol clients and servers. Prior to
7.5
CVE-2026-76088
### Summary An architectural security boundary bypass in inline-detach and MessageInspector allows remote, una
7.5
CVE-2026-76417
A vulnerability in Object Linking and Embedding, 2nd Generation (OLE2) file parser for ClamAV could allow an u
7.5
CVE-2026-76515
A vulnerability in the Object Linking and Embedding, 2nd Generation (OLE2) file parser for ClamAV could allow
7.1
CVE-2026-130781
Incus before 7.6.0 contains a resource exhaustion vulnerability in the storage bucket S3 listener, which buffe