What is the CVSS score of EUVD-2026-19631?

EUVD-2026-19631 has a CVSS 3.1 base score of 8.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Java are affected by EUVD-2026-19631?

Apache Kafka Java producer client versions 3.9.1, 4.0.1, and 4.1.1 contain a buffer use-after-free vulnerability that can cause messages to be silently routed to incorrect topics during batch…. A patch is available.

How to fix or mitigate EUVD-2026-19631?

Within 24 hours: inventory all Kafka Java producer deployments and identify instances running versions ≤3.9.1, ≤4.0.1, or ≤4.1.1 using dependency scanning tools. Within 7 days: prepare and test upgrade to the next minor version beyond affected ranges (minimum 3.9.2, 4.0.2, or 4.1.2 respectively) in a non-production environment and validate message routing integrity. Within 30 days: complete production deployment of patched Kafka versions across all message producer infrastructure and implement enhanced monitoring of topic routing anomalies.

Java EUVD-2026-19631

| CVE-2026-35554 HIGH

Use After Free (CWE-416)

2026-04-07 apache

GHSA-5qcv-4rpc-jp93

Information Disclosure Memory Corruption Apache Use After Free Deserialization Java Suse Red Hat

8.7

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.7 HIGH

AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

SUSE

HIGH

qualitative

Red Hat

6.8 MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Apr 07, 2026 - 13:45 euvd

EUVD-2026-19631

Analysis Generated

Apr 07, 2026 - 13:45 vuln.today

CVE Published

Apr 07, 2026 - 13:07 nvd

HIGH 8.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1,146 maven packages depend on org.apache.kafka:kafka-clients (238 direct, 913 indirect)

Ecosystem-wide dependent count for version 2.8.0.

DescriptionCVE.org

A race condition in the Apache Kafka Java producer client’s buffer pool management can cause messages to be silently delivered to incorrect topics.

When a produce batch expires due to delivery.timeout.ms while a network request containing that batch is still in flight, the batch’s ByteBuffer is prematurely deallocated and returned to the buffer pool. If a subsequent producer batch-potentially destined for a different topic-reuses this freed buffer before the original network request completes, the buffer contents may become corrupted. This can result in messages being delivered to unintended topics without any error being reported to the producer.

Data Confidentiality: Messages intended for one topic may be delivered to a different topic, potentially exposing sensitive data to consumers who have access to the destination topic but not the intended source topic.

Data Integrity: Consumers on the receiving topic may encounter unexpected or incompatible messages, leading to deserialization failures, processing errors, and corrupted downstream data.

This issue affects Apache Kafka versions ≤ 3.9.1, ≤ 4.0.1, and ≤ 4.1.1.

Kafka users are advised to upgrade to 3.9.2, 4.0.2, 4.1.2, 4.2.0, or later to address this vulnerability.

AnalysisAI

Buffer use-after-free in Apache Kafka Java producer client (versions ≤3.9.1, ≤4.0.1, ≤4.1.1) can silently route messages to incorrect topics when batch expiration races with in-flight network requests. CVSS 8.7 (High) with network-accessible attack vector and high complexity. CISA SSVC indicates no active exploitation, non-automatable attack, and partial technical impact. No public exploit identified at time of analysis. EPSS data not provided, but the combination of high CVSS, cross-scope impact (S:C), and dual confidentiality/integrity impact warrants prioritization for environments processing sensitive message streams.

Technical ContextAI

This vulnerability stems from a classic use-after-free race condition (CWE-416) in Apache Kafka's Java producer client buffer pool implementation. When a produce batch exceeds delivery.timeout.ms while the containing network request remains in flight, the producer deallocates the ByteBuffer and returns it to the shared buffer pool prematurely. The freed buffer can then be allocated to a new producer batch-potentially targeting a completely different topic-before the original network request completes. This creates a window where two logically distinct batches share the same physical buffer, enabling memory corruption and cross-topic message contamination. The affected component is the Apache Kafka Clients library (CPE: cpe:2.3:a:apache_software_foundation:apache_kafka_clients), specifically versions 2.8.0 through 3.9.1, 4.0.0 through 4.0.1, and 4.1.0 through 4.1.1. The vulnerability surfaces in multi-topic producer workflows under network latency or backpressure conditions where timeout-driven buffer recycling races with asynchronous I/O completion.

RemediationAI

Vendor-released patches are available: upgrade Apache Kafka Clients to version 3.9.2, 4.0.2, 4.1.2, or 4.2.0 (or any later version) to fully remediate this use-after-free condition. Organizations should prioritize upgrading client libraries in applications producing messages to multiple topics or operating in high-latency network environments. As an interim mitigation for environments unable to immediately upgrade, consider increasing delivery.timeout.ms values to reduce batch expiration frequency, implementing dedicated producer instances per topic to eliminate cross-topic buffer reuse, and deploying comprehensive end-to-end message tracing to detect anomalous cross-topic message delivery. Review consumer error logs for unexpected deserialization failures that may indicate historical exploitation. Full remediation guidance is available in the Apache security advisory at https://lists.apache.org/thread/f07x7j8ovyqhjd1to25jsnqbm6wj01d6. Note that server-side Kafka broker upgrades do not address this client-side vulnerability-affected client libraries must be upgraded independently.