fix(deps): update kafka-client.version to v4.1.2 (release/5.0.x) (patch)#641
Open
renovate[bot] wants to merge 1 commit intorelease/5.0.xfrom
Open
fix(deps): update kafka-client.version to v4.1.2 (release/5.0.x) (patch)#641renovate[bot] wants to merge 1 commit intorelease/5.0.xfrom
renovate[bot] wants to merge 1 commit intorelease/5.0.xfrom
Conversation
eb05b51 to
1bc7682
Compare
1bc7682 to
af15938
Compare
af15938 to
05a6138
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.24.1.1→4.1.2Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition
CVE-2026-35554 / GHSA-5qcv-4rpc-jp93
More information
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.
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.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation
CVE-2026-33557 / GHSA-28jg-cgg7-j4wc
More information
Details
A security vulnerability has been identified in Apache Kafka. By default, the broker property
sasl.oauthbearer.jwt.validator.classis set toorg.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 thepreferred_usernameset to any user, and the broker will accept it.Apache advises Kafka users using kafka v4.1.0 or v4.1.1 to set the config
sasl.oauthbearer.jwt.validator.classtoorg.apache.kafka.common.security.oauthbearer.BrokerJwtValidatorexplicitly 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.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)* 0-3 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.