From 90f6da07e925edea9a74383a306e5a03e2eef7dc Mon Sep 17 00:00:00 2001
From: Filipe Ferreira <55758354+filipecamargos@users.noreply.github.com>
Date: Wed, 8 Apr 2026 10:33:42 -0400
Subject: [PATCH] Improve GHSA-5qcv-4rpc-jp93

---
 .../GHSA-5qcv-4rpc-jp93.json                  | 22 +++++++++++++++++--
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/advisories/unreviewed/2026/04/GHSA-5qcv-4rpc-jp93/GHSA-5qcv-4rpc-jp93.json b/advisories/unreviewed/2026/04/GHSA-5qcv-4rpc-jp93/GHSA-5qcv-4rpc-jp93.json
index 44b179e50d0aa..598f8ff3888ca 100644
--- a/advisories/unreviewed/2026/04/GHSA-5qcv-4rpc-jp93/GHSA-5qcv-4rpc-jp93.json
+++ b/advisories/unreviewed/2026/04/GHSA-5qcv-4rpc-jp93/GHSA-5qcv-4rpc-jp93.json
@@ -1,11 +1,12 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-5qcv-4rpc-jp93",
-  "modified": "2026-04-07T18:31:34Z",
+  "modified": "2026-04-07T18:32:42Z",
   "published": "2026-04-07T15:30:50Z",
   "aliases": [
     "CVE-2026-35554"
   ],
+  "summary": "Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition",
   "details": "A race condition in the Apache Kafka Java producer client’s buffer pool management can cause messages to be silently delivered to incorrect topics.\n\nWhen 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.\n\n\nData Confidentiality:\nMessages 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.\n\nData Integrity:\nConsumers on the receiving topic may encounter unexpected or incompatible messages, leading to deserialization failures, processing errors, and corrupted downstream data.\n\nThis issue affects Apache Kafka versions ≤ 3.9.1, ≤ 4.0.1, and  ≤ 4.1.1.\n\nKafka users are advised to upgrade to 3.9.2, 4.0.2, 4.1.2, 4.2.0, or later to address this vulnerability.",
   "severity": [
     {
@@ -13,7 +14,24 @@
       "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N"
     }
   ],
-  "affected": [],
+  "affected": [
+    {
+      "package": {
+        "ecosystem": "Maven",
+        "name": "org.apache.kafka:kafka-clients"
+      },
+      "ranges": [
+        {
+          "type": "ECOSYSTEM",
+          "events": [
+            {
+              "introduced": "0"
+            }
+          ]
+        }
+      ]
+    }
+  ],
   "references": [
     {
       "type": "ADVISORY",