CVE 9.8 CRITICAL

Apache Druid: Kerberos authenticaton chooses a cryptographically unsecure secret if not configured explicitly._CVE-2025-59390

9.8 / 10
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Description

Apache Druid’s Kerberos authenticator uses a weak fallback secret when the `druid.auth.authenticator.kerberos.cookieSignatureSecret` configuration is not explicitly set. In this case, the secret is generated using `ThreadLocalRandom`,
which is not a crypto-graphically secure random number generator. This
may allow an attacker to predict or brute force the secret used to sign
authentication cookies, potentially enabling token forgery or
authentication bypass. Additionally, each process generates its own
fallback secret, resulting in inconsistent secrets across nodes. This
causes authentication failures in distributed or multi-broker
deployments, effectively leading to a incorrectly configured clusters. Users are
advised to configure a strong `druid.auth.authenticator.kerberos.cookieSignatureSecret`



This issue affects Apache Druid: through 34.0.0.

Users are recommended to upgrade to version 35.0.0, which fixes the issue making it mandatory to set `druid.auth.authenticator.kerberos.cookieSignatureSecret` when using the Kerberos authenticator. Services will fail to come up if the secret is not set.

AI Analysis

Apache Druid's Kerberos authenticator uses a weak fallback secret, allowing potential token forgery or authentication bypass.

Basic Information

ID CVE-2025-59390
Source apache
Published Nov 26, 2025 at 08:50
Modified Nov 26, 2025 at 14:59

Affected Product

Vendor Apache Software Foundation
Product Apache Druid
Affected Versions Apache Software Foundation Apache Druid 0

CWE Classification

AI Assessment

AI Score 9.8 / 10
AI Severity Critical
Vendor Apache Foundation
Product Apache Druid
Version through 34.0.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.