MediumGHSA-wf66-mphr-4c4rBIT-kafka-2026-33558CVE-2026-33558

Apache Kafka exposes sensitive information in its DEBUG logs

Published 20 Apr 2026 · Updated 10 Sept 2026

Is your project on an affected org.apache.kafka:kafka-clients?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=0.11.0 <3.9.2
Fixed in
3.9.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=3.9.2 -DforceVersion=true
Affected
>=4.0.0 <4.0.1
Fixed in
4.0.1
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=4.0.1 -DforceVersion=true

Details

Information exposure vulnerability has been identified in Apache Kafka.

The NetworkClient component will output entire requests and responses information in the DEBUG log level in the logs. By default, the log level is set to INFO level. If the DEBUG level is enabled, the sensitive information will be exposed via the requests and responses output log. The entire lists of impacted requests and responses are:

  • AlterConfigsRequest
  • AlterUserScramCredentialsRequest
  • ExpireDelegationTokenRequest
  • IncrementalAlterConfigsRequest
  • RenewDelegationTokenRequest
  • SaslAuthenticateRequest
  • createDelegationTokenResponse
  • describeDelegationTokenResponse
  • SaslAuthenticateResponse

This issue affects Apache Kafka: from any version supported the listed API above through v3.9.1, v4.0.0. Apache advises Kafka users to upgrade to v3.9.2, v4.0.1, or later to avoid this vulnerability.

Is GHSA-wf66-mphr-4c4r in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.kafka:kafka-clients, and gives you the command that fixes it.

More advisories for org.apache.kafka:kafka-clients

  • CriticalCVE-2026-33557Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation · 20 Apr 2026
  • HighCVE-2026-35554Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition · 7 Apr 2026
  • MediumCVE-2025-27817Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability · 10 Jun 2025
  • MediumCVE-2024-31141Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider · 19 Nov 2024
  • MediumCVE-2017-12610Improper Authentication in Apache Kafka · 13 May 2022
  • MediumCVE-2021-38153Observable Discrepancy in Apache Kafka · 23 Sept 2021
org.apache.kafka:kafka-clients security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.