Skip to main content
Public proof of conceptFix available

CVE-2025-27817

A public proof of concept exists; no exploitation attested.

  • Published2025-06-10
  • Fixed in3.9.1
  • WeaknessCWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2025-06-1008:15CVE publishedNVD

Versions per branch

NVD · OSV
Apache kafka
BranchAffectedFixed in
3.x≥ 3.1.0, < 3.9.13.9.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Kafka Clientother versions: not affected
    Affected
    • ≥ 3.1.0, ≤ 3.9.0no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-06-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-nifiWolfiall versions · fixed in 2.4.0-r4and 2 other packages
  • apache-nifiChainguardall versions · fixed in 2.4.0-r4and 2 other packages
  • apicurio-registryWolfiall versions · fixed in 3.0.9-r1and 2 other packages
  • apicurio-registryChainguardall versions · fixed in 3.0.9-r1and 2 other packages
  • conductorMinimOSall versions · fixed in 3.32.1-r0and 1 other package
  • druidWolfiall versions · fixed in 33.0.0-r4and 1 other package
  • druidChainguardall versions · fixed in 33.0.0-r4and 1 other package
  • io.root.org.apache.kafka:kafka-clientsRoot:Mavenall versions · fixed in 3.6.0-root.io.1

44 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-27817 Red Hat Product Security2 products fixed

    org.apache.kafka: Kafka Client Arbitrary File Read SSRF

  • RHSA-2025:23417 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Streams for Apache Kafka 3.1.0 release and security update

  • RHSA-2025:9922 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Streams for Apache Kafka 2.9.1 release and security update

Full record on NVD

Fix

  1. Update Apache kafka to 3.9.1
  2. Vendor fix Red Hat Product Security RHSA-2025:23417 · 1 productBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2025:23417 · 1 productTo mitigate this flaw, explicitly set the allowed urls in SASL JAAS configuration using the system property "-Dorg.apache.kafka.sasl.oauthbearer.allowed.urls".

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2025-06-10
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-vgq5-3255-v292

Frequently asked questions

What is CVE-2025-27817?

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 CVE-2025-27817 actively exploited?

Active exploitation of CVE-2025-27817 has not been confirmed. Its EPSS score was 69.8% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-27817?

CVE-2025-27817 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running kafka? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record