CVE-2025-27817
MediumExploitedApache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability
Published Jun 10, 2025 · Updated Sep 10, 2026 · Also known as BIT-kafka-2025-27817, GHSA-vgq5-3255-v292, ROOT-APP-MAVEN-CVE-2025-27817
Key Facts
Patch immediately- CVE-2025-27817 is a medium-severity vulnerability (CVSS 8.6 v4) affecting Kafka (Apache), apache-nifi (chainguard), apicurio-registry (chainguard) and 17 more products.
- It is exploited in the wild, listed in Industry KEV feed since Apr 8, 2026. No public exploit code is known.
- EPSS estimates a 69% probability of exploitation in the next 30 days.
- Fixed versions are available, including Kafka 3.9.1, Kafka 3.9.1-1.ph4, Kafka 3.9.1-1.ph5.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v4
8.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
EPSS (30-day exploit likelihood)
69%
Higher than 99.3% of all scored CVEs
Exploited in the wild
Yes
1 catalog listing
Public exploit code
None known
Get the full CVE-2025-27817 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | Apr 8, 2026 | n/a | Not reported |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
39 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| KafkaApache | >= 3.1.0 | 3.9.1 |
| apache-nifichainguard | See advisory | 2.4.0-r4 |
| apicurio-registrychainguard | See advisory | 3.0.9-r1 |
| debezium-connector-spanner-3.0chainguard | See advisory | 3.0.8-r5 |
| druidchainguard | See advisory | 33.0.0-r4 |
Patched Releases
Kafka
3.9.1, 3.9.1-1.ph4, 3.9.1-1.ph5
apache-nifi
2.4.0-r4
apicurio-registry
3.0.9-r1
conductor
3.32.1-r0
conductor-fips
3.32.1-r0
debezium-connector-spanner-3.0
3.0.8-r5
druid
33.0.0-r4
io.root.org.apache.kafka:kafka-clients
3.6.0-root.io.1, 3.6.0-root.io.2, 3.6.0-root.io.3, 3.7.1-root.io.1, 3.7.1-root.io.2, 3.7.1-root.io.3, 3.8.1-root.io.1, 3.8.1-root.io.2, 3.8.1-root.io.3, 3.8.1-root.io.4, 3.9.1-root.io.1, 3.9.1-root.io.2, 3.9.1-root.io.3, 3.9.1-root.io.4
logstash-8
8.18.2-r2
opensearch-2
2.19.1-r5, 2.19.4-r0
opensearch-3
3.0.0-r2
org.apache.kafka:kafka-clients
3.4.0+sp999, 3.6.0-aikido.3, 3.7.1-aikido.2, 3.7.1-aikido.3, 3.8.1-aikido.3, 3.8.1-aikido.4, 3.9.1, 3.9.1-aikido.4
prometheus-jmx-exporter
0.46.0-r6
seal.sp1.org.apache.kafka:kafka-clients
3.4.0+sp999
strimzi-kafka-operator
0.45.1-r3, 0.46.0-r6
strimzi-kafka-operator-0.45
0.45.2-r0
thingsboard
4.0.1-r6
wildfly
36.0.1-r5
zipkin
3.5.1-r2
Timeline
Publicly disclosed
Jun 10, 2025
Added to Industry KEV feed
Apr 8, 2026
Last updated
Sep 10, 2026
Weakness Type
- CWE-918 Server-Side Request Forgery (SSRF)
References
- advisoryRHSA-2025:23417
- advisoryRHSA-2025:9922
- advisoryGHSA advisory
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27817.json
- advisoryhttps://kafka.apache.org/cve-list
FAQ
Common Questions.
A possible arbitrary file read and SSRF vulnerability has been identified in Apache Kafka Client.
Affected: Kafka (Apache) versions >= 3.1.0; apache-nifi (chainguard); apicurio-registry (chainguard), among others. The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since Apr 8, 2026.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Kafka 3.9.1, Kafka 3.9.1-1.ph4, Kafka 3.9.1-1.ph5.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2025-27817 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo