{"id":"CVE-2025-27817","aliases":["BIT-kafka-2025-27817","CLSA-2025-1752019395","CLSA-2026-1783991065","CLSA-2026-1789425652","EUVD-2025-17640","GHSA-2x2g-32r7-p4x8","GHSA-5qcv-4rpc-jp93","GHSA-vgq5-3255-v292","GHSA-wf66-mphr-4c4r","RHLW-2026-f7c61b4b79130a3c","ROOT-APP-MAVEN-CVE-2025-27817"],"status":"published","title":"Apache Kafka Client: Arbitrary file read and SSRF vulnerability","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. \n\nSince 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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-12","score":0.69836,"percentile":0.9938,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":true,"fix_available":true},"cwes":["CWE-918"],"published":"2025-06-10T07:55:14Z","modified":"2026-11-02T19:46:15Z","exploits":[{"source":"pocgithub","id":"iSee857/CVE-2025-27817","title":"iSee857/CVE-2025-27817","date":"2025-07-04","url":"https://github.com/iSee857/CVE-2025-27817"},{"source":"pocgithub","id":"oriolrius/kafka-keycloak-oauth","title":"oriolrius/kafka-keycloak-oauth","date":"2025-10-13","url":"https://github.com/oriolrius/kafka-keycloak-oauth"},{"source":"nuclei","id":"CVE-2025-27817","title":"Apache Kafka Client - Arbitrary File Read","type":"detection template","url":"https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-27817.yaml"}],"fixes":[{"ecosystem":"Maven","package":"org.apache.kafka:kafka-clients","fixed_in":["3.9.1"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"kafka","fixed_in":["3.9.1"],"sources":["osv"]},{"ecosystem":"TuxCare:Maven","package":"org.apache.kafka:kafka-clients","fixed_in":["3.2.2-tuxcare.1"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"io.root.org.apache.kafka:kafka-clients","fixed_in":["3.6.0-root.io.1","3.8.1-root.io.1","3.7.1-root.io.1","3.8.1-root.io.2","3.6.0-root.io.2","3.6.0-root.io.3","3.7.1-root.io.2","3.8.1-root.io.3","3.7.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"],"sources":["osv"]},{"ecosystem":"Root:Maven","package":"org.apache.kafka:kafka-clients","fixed_in":["3.6.0-aikido.3","3.7.1-aikido.2","3.8.1-aikido.3","3.7.1-aikido.3","3.8.1-aikido.4","3.9.1-aikido.4"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.1.0"},{"fixed":"3.9.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"kafka","ranges":[{"type":"SEMVER","events":[{"introduced":"3.1.0"},{"fixed":"3.9.1"}]}]},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.3"},{"fixed":"3.2.3.tuxcare.1"}]}],"versions":["3.2.3","3.2.3.tuxcare"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.kafka:kafka_2.12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.3"},{"fixed":"3.2.3.tuxcare.1"}]}],"versions":["3.2.3","3.2.3.tuxcare"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.kafka:kafka_2.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.3"},{"fixed":"3.2.3.tuxcare.1"}]}],"versions":["3.2.3","3.2.3.tuxcare"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.7.1"},{"fixed":"3.7.1-tuxcare.1"}]}],"versions":["3.7.1"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.2"},{"fixed":"3.2.2-tuxcare.1"}]}],"versions":["3.2.2"]},{"source":"osv","ecosystem":"Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.1.0"},{"fixed":"3.9.1"}]}],"versions":["3.1.0","3.1.1","3.1.2","3.2.0","3.2.1","3.2.2","3.2.3","3.3.0","3.3.1","3.3.2","3.4.0","3.4.1","3.5.0","3.5.1","3.5.2","3.6.0","3.6.1","3.6.2","3.7.0","3.7.1","3.7.2","3.8.0","3.8.1","3.9.0"]},{"source":"osv","ecosystem":"Red Hat Lightwell:Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.2.rhlw-00004"}]}],"versions":["0.10.0.0","0.10.0.1","0.10.1.0","0.10.1.1","0.10.2.0","0.10.2.1","0.10.2.2","0.11.0.0","0.11.0.1","0.11.0.2","0.11.0.3","0.8.2-beta","0.8.2.0","0.8.2.1","0.8.2.2","0.9.0.0","0.9.0.1","1.0.0","1.0.1","1.0.2","1.1.0","1.1.1","2.0.0","2.0.1","2.1.0","2.1.1","2.2.0","2.2.1","2.2.2","2.3.0","2.3.1","2.4.0","2.4.1","2.5.0","2.5.1","2.6.0","2.6.1","2.6.2","2.6.3","2.7.0","2.7.1","2.7.2","2.8.0","2.8.1","2.8.2","3.0.0","3.0.1","3.0.2","3.1.0","3.1.1","3.1.2","3.2.0","3.2.1","3.2.2","3.2.3","3.3.0","3.3.1","3.3.2","3.4.0","3.4.1","3.5.0","3.5.1","3.5.2","3.6.0","3.6.1","3.6.2"],"bundled":4},{"source":"osv","ecosystem":"Root:Maven","package":"io.root.org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.0-root.io.1"},{"fixed":"3.8.1-root.io.1"},{"fixed":"3.7.1-root.io.1"},{"fixed":"3.8.1-root.io.2"},{"fixed":"3.6.0-root.io.2"},{"fixed":"3.6.0-root.io.3"},{"fixed":"3.7.1-root.io.2"},{"fixed":"3.8.1-root.io.3"},{"fixed":"3.7.1-root.io.3"},{"fixed":"3.8.1-root.io.4"},{"fixed":"3.9.1-root.io.1"},{"fixed":"3.9.1-root.io.2"},{"fixed":"3.9.1-root.io.3"},{"fixed":"3.9.1-root.io.4"}]}]},{"source":"osv","ecosystem":"Root:Maven","package":"org.apache.kafka:kafka-clients","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.0-aikido.3"},{"fixed":"3.7.1-aikido.2"},{"fixed":"3.8.1-aikido.3"},{"fixed":"3.7.1-aikido.3"},{"fixed":"3.8.1-aikido.4"},{"fixed":"3.9.1-aikido.4"}]}]}],"products":[{"vendor":"apache","product":"kafka"},{"vendor":"apache software foundation","product":"apache kafka client"}],"references":[{"url":"https://kafka.apache.org/cve-list","tags":["vendor-advisory","Vendor Advisory","advisory","web"]},{"url":"http://www.openwall.com/lists/oss-security/2025/06/09/1","tags":["Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-27817","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-vgq5-3255-v292","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27817.json","tags":["advisory"]},{"url":"https://github.com/apache/kafka","tags":["package"]},{"url":"https://repo.maven.apache.org/maven2","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/31xxx/CVE-2024-31141.json","tags":["advisory"]},{"url":"https://lists.apache.org/thread/9whdzfr0zwdhr364604w5ssnzmg4v2lv","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-31141","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-2x2g-32r7-p4x8","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33558.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-33558","tags":["advisory"]},{"url":"https://lists.apache.org/thread/pz5g4ky3h0k91tfd14p0dzqjp80960kl","tags":["article"]},{"url":"https://github.com/advisories/GHSA-wf66-mphr-4c4r","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/35xxx/CVE-2026-35554.json","tags":["advisory"]},{"url":"https://lists.apache.org/thread/f07x7j8ovyqhjd1to25jsnqbm6wj01d6","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-35554","tags":["advisory"]},{"url":"https://issues.apache.org/jira/browse/KAFKA-19012","tags":["report"]},{"url":"https://github.com/advisories/GHSA-5qcv-4rpc-jp93","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-27817","title":"Apache Kafka Client: Arbitrary file read and SSRF vulnerability","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. \n\nSince 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.","status":"published","published":"2025-06-10T07:55:14.422Z","modified":"2025-06-10T15:15:40.843Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"adp"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:32:42.078906Z"}],"euvd":[{"id":"EUVD-2025-17640","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. \n\nSince 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.","status":"published","published":"2025-06-10T07:55:14Z","modified":"2025-06-10T15:15:40Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T20:32:26.841647Z"}],"ghsa":[{"id":"GHSA-vgq5-3255-v292","title":"Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability","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. \n\nSince 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.","status":"published","published":"2025-06-10T09:30:31Z","modified":"2025-06-10T20:41:37Z","cvss":[{"version":"4.0","score":6.2,"vector":"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","level":"medium"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:38:46.901955Z"}],"nvd":[{"id":"CVE-2025-27817","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. \n\nSince 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.","status":"published","published":"2025-06-10T08:15:22.367Z","modified":"2026-06-17T09:04:16.3Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:11:11.4244Z"}],"osv":[{"id":"CVE-2025-27817","title":"Apache Kafka Client: Arbitrary file read and SSRF vulnerability","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. \n\nSince 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.","status":"published","published":"2025-06-10T07:55:14.422Z","modified":"2026-10-28T02:30:45.410210179Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T15:44:47.708311Z"},{"id":"GHSA-vgq5-3255-v292","title":"Apache Kafka Client Arbitrary File Read and Server Side Request Forgery Vulnerability","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. \n\nSince 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.","status":"published","published":"2025-06-10T09:30:31Z","modified":"2026-09-10T03:50:25.468399734Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"},{"version":"4.0","score":6.2,"vector":"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","level":"medium"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T15:46:57.348035Z"},{"id":"RHLW-2026-f7c61b4b79130a3c","title":"Lightwell Security Advisory: kafka-clients 3.6.2.rhlw-00004","description":"Red Hat Lightwell has released org.apache.kafka:kafka-clients 3.6.2.rhlw-00004 with backported fixes for CVE-2024-31141, CVE-2025-27817, CVE-2026-33558, and CVE-2026-35554.\n\nCVE-2024-31141: Apache Kafka Clients: Privilege escalation to filesystem read-access via automatic ConfigProvider\n\nCVE-2025-27817: Apache Kafka Client: Arbitrary file read and SSRF vulnerability\n\nCVE-2026-33558: Apache Kafka, Apache Kafka Clients: Information Exposure Through Network Client Log Output\n\nCVE-2026-35554: Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition\n\nThis patched artifact is a drop-in replacement for org.apache.kafka:kafka-clients 3.6.2 from Maven Central.","status":"published","published":"2026-10-15T01:32:14Z","modified":"2026-10-27T08:58:02.021257685Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:59.135214Z"},{"id":"ROOT-APP-MAVEN-CVE-2025-27817","title":"CVE-2025-27817 in io.root.org.apache.kafka:kafka-clients - Patched by Root","description":"Root has patched CVE-2025-27817 in the io.root.org.apache.kafka:kafka-clients package for Root:Maven. Multiple fixed versions available.","status":"published","published":"2026-06-30T08:29:27Z","modified":"2026-06-30T13:15:14.179079061Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T15:53:27.066589Z"},{"id":"BIT-kafka-2025-27817","title":"Apache Kafka Client: Arbitrary file read and SSRF vulnerability","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. \n\nSince 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.","status":"published","published":"2025-07-12T05:43:25.32Z","modified":"2026-09-08T08:48:23.88086868Z","updated_at":"2026-11-02T15:28:31.782692Z"},{"id":"CLSA-2025-1752019395","title":"TuxCare security update for org.apache.kafka (5 CVEs)","description":"TuxCare rebuilt 3 org.apache.kafka packages to address 5 CVEs. Fixed in 3.2.3.tuxcare.1.","status":"published","published":"2026-08-04T14:52:04Z","modified":"2026-11-02T19:45:07.399198232Z","updated_at":"2026-11-02T20:30:40.499236Z"},{"id":"CLSA-2026-1783991065","title":"TuxCare security update for org.apache.kafka:kafka-clients (2 CVEs)","description":"TuxCare rebuilt org.apache.kafka:kafka-clients to address 2 CVEs. Fixed in 3.7.1-tuxcare.1.","status":"published","published":"2026-08-04T14:52:43Z","modified":"2026-11-02T19:45:38.663756006Z","updated_at":"2026-11-02T20:30:13.950198Z"},{"id":"CLSA-2026-1789425652","title":"TuxCare security update for org.apache.kafka:kafka-clients (1 CVE)","description":"TuxCare rebuilt org.apache.kafka:kafka-clients to address 1 CVE. Fixed in 3.2.2-tuxcare.1.","status":"published","published":"2026-09-14T22:40:52Z","modified":"2026-11-02T19:46:15.50849391Z","updated_at":"2026-11-02T20:29:33.792105Z"}]}}