RHSA-2025:12511HighCVSS 8.8

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

Published
August 1, 2025
Last Modified
November 6, 2026

🔗 CVE IDs covered (13)

CVE-2024-13009 →CVE-2024-56128 →CVE-2025-1634 →CVE-2025-24970 →CVE-2025-25193 →CVE-2025-48734 →CVE-2025-49574 →CVE-2024-6763 →CVE-2024-31141 →CVE-2024-47535 →CVE-2025-48924 →CVE-2025-53864 →CVE-2023-1370 →

📋 Description

CVE-2023-1370 — json-smart: Uncontrolled Resource Consumption vulnerability in json-smart (Resource Exhaustion) CVE-2024-6763 — org.eclipse.jetty:jetty-http: jetty: Jetty URI parsing of invalid authority CVE-2024-13009 — jetty-server: Jetty: Gzip Request Body Buffer Corruption CVE-2024-31141 — kafka-clients: privilege escalation to filesystem read-access via automatic ConfigProvider CVE-2024-47535 — netty: Denial of Service attack on windows app using Netty CVE-2024-56128 — kafka: Apache Kafka: SCRAM authentication vulnerable to replay attacks when used without encryption CVE-2025-1634 — io.quarkus:quarkus-resteasy: Memory Leak in Quarkus RESTEasy Classic When Client Requests Timeout CVE-2025-24970 — io.netty:netty-handler: SslHandler doesn't correctly validate packets which can lead to native crash when using native SSLEngine CVE-2025-25193 — netty: Denial of Service attack on windows app using Netty CVE-2025-48734 — commons-beanutils: Apache Commons BeanUtils: PropertyUtilsBean does not suppresses an enum's declaredClass property by default CVE-2025-48924 — commons-lang/commons-lang: org.apache.commons/commons-lang3: Uncontrolled Recursion vulnerability in Apache Commons Lang CVE-2025-49574 — io.quarkus/quarkus-vertx: Quarkus potential data leak CVE-2025-53864 — com.nimbusds/nimbus-jose-jwt: Uncontrolled recursion in Connect2id Nimbus JOSE + JWT

🎯 Affected products1

  • Streams for Apache Kafka 3.0.0

✅ Remediation

Before 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 Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: For applications in which an untrusted party can specify Apache Kafka Client configuration, disable automatic configuration providers by setting the JVM system property org.apache.kafka.automatic.config.providers=none. For Kafka Connect workers that must use the listed providers, restrict them with appropriate allowlist.pattern and allowed.paths settings. Upgrade kafka-clients to version 3.8.0 or later, or apply the applicable vendor fix. The system-property restriction is not recommended for Kafka Clients or Kafka Connect deployments where users are trusted with disk and environment access, or for Kafka Broker, Kafka MirrorMaker 2.0, Kafka Streams, and Kafka command-line tools. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Currently, no mitigation is available for this vulnerability.

🔗 References (18)