MediumGHSA-vgq5-3255-v292BIT-kafka-2025-27817CVE-2025-27817

Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability

Published 10 Jun 2025 · 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 package

Affected
>=3.1.0 <3.9.1
Fixed in
3.9.1
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.1 -DforceVersion=true

Details

A possible arbitrary file read and SSRF vulnerability has been identified in Apache Kafka Client. Apache Kafka Clients accept configuration data for setting the SASL/OAUTHBEARER connection with the brokers, including "sasl.oauthbearer.token.endpoint.url" and "sasl.oauthbearer.jwks.endpoint.url". Apache Kafka allows clients to read an arbitrary file and return the content in the error log, or sending requests to an unintended location. In applications where Apache Kafka Clients configurations can be specified by an untrusted party, attackers may use the "sasl.oauthbearer.token.endpoint.url" and "sasl.oauthbearer.jwks.endpoint.url" configuratin to read arbitrary contents of the disk and environment variables or make requests to an unintended location. In particular, this flaw may be used in Apache Kafka Connect to escalate from REST API access to filesystem/environment/URL access, which may be undesirable in certain environments, including SaaS products.

Since Apache Kafka 3.9.1/4.0.0, we have added a system property ("-Dorg.apache.kafka.sasl.oauthbearer.allowed.urls") to set the allowed urls in SASL JAAS configuration. In 3.9.1, it accepts all urls by default for backward compatibility. However in 4.0.0 and newer, the default value is empty list and users have to set the allowed urls explicitly.

Is GHSA-vgq5-3255-v292 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-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.