All errata/sisyphus/ALT-PU-2026-6756-3
ALT-PU-2026-6756-3

Package update kafka in branch sisyphus

Version4.2.0-alt1
Task#408614
Published2026-08-19
Max severityCRITICAL
Severity:

Closed issues (6)

BDU:2026-06346
HIGH8.7

Уязвимость диспетчера сообщений Apache Kafka, связанная с использованием памяти после её освобождения, позволяющая нарушителю оказать воздействие на конфиденциальность и целостность защищаемой информации

Published: 2026-05-05Modified: 2026-07-22
CVSS 3.xHIGH 8.7
CVSS:3.x/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
CVSS 2.0HIGH 7.1
CVSS:2.0/AV:N/AC:H/Au:N/C:C/I:C/A:N
References
BDU:2026-09403
CRITICAL9.1

Уязвимость класса org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator диспетчера сообщений Apache Kafka, позволяющая нарушителю обойти ограничения безопасности и получить несанкционированный доступ к защищаемой информации

Published: 2026-07-07
CVSS 3.xCRITICAL 9.1
CVSS:3.x/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS 2.0CRITICAL 9.4
CVSS:2.0/AV:N/AC:L/Au:N/C:C/I:C/A:N
References
CVE-2026-33557
CRITICAL9.1

A possible security vulnerability has been identified in Apache Kafka. By default, the broker property `sasl.oauthbearer.jwt.validator.class` is set to `org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator`. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the `preferred_username` set to any user, and the broker will accept it. We advise the Kafka users using kafka v4.1.0 or v4.1.1 to set the config `sasl.oauthbearer.jwt.validator.class` to `org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator` explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.

Published: 2026-04-20Modified: 2026-07-14
CVSS 3.xCRITICAL 9.1
CVSS:3.x/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
CVE-2026-35554
HIGH8.7

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.

Published: 2026-04-07Modified: 2026-08-17
CVSS 3.xHIGH 8.7
CVSS:3.x/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
References
GHSA-28jg-cgg7-j4wc
CRITICAL9.1

Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation

Published: 2026-04-20Modified: 2026-04-24
CVSS 3.xCRITICAL 9.1
CVSS:3.x/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
GHSA-5qcv-4rpc-jp93
HIGH8.7

Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition

Published: 2026-04-07Modified: 2026-04-13
CVSS 3.xHIGH 8.7
CVSS:3.x/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
References