Skip to content

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
renovate/release/5.0.x-patch-kafka-client.version
Open

fix(deps): update kafka-client.version to v4.1.2 (release/5.0.x) (patch)#641
renovate[bot] wants to merge 1 commit intorelease/5.0.xfrom
renovate/release/5.0.x-patch-kafka-client.version

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 23, 2026

This PR contains the following updates:

Package Change Age Confidence
org.apache.kafka:kafka_2.13 4.1.14.1.2 age confidence
org.apache.kafka:kafka-streams-test-utils 4.1.14.1.2 age confidence
org.apache.kafka:kafka-server-common 4.1.14.1.2 age confidence
org.apache.kafka:kafka-transaction-coordinator 4.1.14.1.2 age confidence
org.apache.kafka:kafka-group-coordinator 4.1.14.1.2 age confidence
org.apache.kafka:kafka-raft 4.1.14.1.2 age confidence
org.apache.kafka:kafka-metadata 4.1.14.1.2 age confidence
org.apache.kafka:kafka-streams 4.1.14.1.2 age confidence
org.apache.kafka:kafka-clients 4.1.14.1.2 age confidence
org.apache.kafka:kafka-server 4.1.14.1.2 age confidence

Apache 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 Score: 8.7 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

References

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.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.

Apache advises 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.

Severity

  • CVSS Score: 9.1 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • Between 12:00 AM and 03:59 AM, only on Monday (* 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Mar 23, 2026
@renovate renovate Bot enabled auto-merge (squash) March 23, 2026 00:46
@renovate renovate Bot force-pushed the renovate/release/5.0.x-patch-kafka-client.version branch from eb05b51 to 1bc7682 Compare March 23, 2026 02:00
@renovate renovate Bot requested a review from a team March 23, 2026 05:03
@renovate renovate Bot force-pushed the renovate/release/5.0.x-patch-kafka-client.version branch from 1bc7682 to af15938 Compare March 30, 2026 05:02
@renovate renovate Bot added the security label Apr 13, 2026
@renovate renovate Bot force-pushed the renovate/release/5.0.x-patch-kafka-client.version branch from af15938 to 05a6138 Compare April 20, 2026 05:10
@renovate renovate Bot added security and removed security labels Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants