CVE-2025-27817

Apache Kafka Client: Arbitrary file read and SSRF vulnerability

Published Jun 10, 2025 CVSS 3.1 · 7.5 High EPSS 69.8% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-17640 Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability
Github GHSA Github GHSA GHSA-vgq5-3255-v292 Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability
History
Type Values Removed Values Added
Metrics epss

{'score': 0.00015}

epss

{'score': 0.00041}

Type Values Removed Values Added
First Time appeared Apache
Apache kafka
CPEs cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:*
Vendors & Products Apache
Apache kafka
Type Values Removed Values Added
First Time appeared Redhat
Redhat amq Streams
CPEs cpe:/a:redhat:amq_streams:2.9::el9
Vendors & Products Redhat
Redhat amq Streams
Type Values Removed Values Added
Weaknesses CWE-918
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Apache Kafka Client: Arbitrary file read and SSRF vulnerability
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Jun 10, 2025, 3:15 PM
Reserved
Mar 7, 2025, 8:12 AM
Status
Analyzed
Published
Jun 10, 2025, 8:15 AM
Modified
Jun 17, 2026, 9:04 AM
Severity
Important
Public date
Jun 10, 2025, 7:55 AM