Insertion of Sensitive Information into Log File Affecting org.apache.kafka:kafka-clients package, versions [0.11.0,3.9.2)[4.0.0,4.0.1)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Insertion of Sensitive Information into Log File vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGAPACHEKAFKA-16300072
- published26 Apr 2026
- disclosed20 Apr 2026
- creditLuke Chen, Alyssa Huang
Introduced: 20 Apr 2026
NewCVE-2026-33558 (opens in a new tab)How to fix?
Upgrade org.apache.kafka:kafka-clients to version 3.9.2, 4.0.1 or higher.
Overview
org.apache.kafka:kafka-clients is a streaming platform that can publish and subscribe to streams of records, store streams of records in a fault-tolerant durable way, and process streams of records as they occur.
Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File. Kafka is vulnerable to the disclosure of sensitive information via the toString methods of IncrementalAlterConfigsRequest and AlterUserScramCredentialsRequest. An attacker can expose config values, SCRAM salts, and salted passwords by triggering request logging or any code path that renders these request objects as strings. This leaks administrative secrets and credential material into logs and diagnostics, allowing unauthorized readers of those logs to recover protected configuration values and authentication data.
Workarounds
- Keep Kafka clients at the default
INFOlog level and do not enableDEBUGlogging forNetworkClient, so request and response objects are not rendered into logs, and sensitive config values, SCRAM salts, and salted passwords are not exposed.