Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider
Published 19 Nov 2024 · Updated 10 Sept 2026
Is your project on an affected org.apache.kafka:kafka-clients?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=2.3.0 <3.7.1
- Fixed in
- 3.7.1
mvn versions:use-dep-version -Dincludes=org.apache.kafka:kafka-clients -DdepVersion=3.7.1 -DforceVersion=trueDetails
Files or Directories Accessible to External Parties, Improper Privilege Management vulnerability in Apache Kafka Clients.
Apache Kafka Clients accept configuration data for customizing behavior, and includes ConfigProvider plugins in order to manipulate these configurations. Apache Kafka also provides FileConfigProvider, DirectoryConfigProvider, and EnvVarConfigProvider implementations which include the ability to read from disk or environment variables. In applications where Apache Kafka Clients configurations can be specified by an untrusted party, attackers may use these ConfigProviders to read arbitrary contents of the disk and environment variables.
In particular, this flaw may be used in Apache Kafka Connect to escalate from REST API access to filesystem/environment access, which may be undesirable in certain environments, including SaaS products. This issue affects Apache Kafka Clients: from from 2.3.0 through 3.5.2, 3.6.0 through 3.6.2, and 3.7.0.
Users with affected applications are recommended to upgrade kafka-clients to version >=3.8.0, and set the JVM system property "org.apache.kafka.automatic.config.providers=none". Users of Kafka Connect with one of the listed ConfigProvider implementations specified in their worker config are also recommended to add appropriate "allowlist.pattern" and "allowed.paths" to restrict their operation to appropriate bounds.
For users of Kafka Clients or Kafka Connect in environments that trust users with disk and environment variable access, it is not recommended to set the system property. For users of the Kafka Broker, Kafka MirrorMaker 2.0, Kafka Streams, and Kafka command-line tools, it is not recommended to set the system property.
Is GHSA-2x2g-32r7-p4x8 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
- MediumCVE-2026-33558Apache Kafka exposes sensitive information in its DEBUG logs · 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-2017-12610Improper Authentication in Apache Kafka · 13 May 2022
- MediumCVE-2021-38153Observable Discrepancy in Apache Kafka · 23 Sept 2021
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.