CVE-2025-59390CWE-338

Apache Druid: Kerberos authenticaton chooses a cryptographically unsecure secret if not configured explicitly.

Critical · published November 26, 2025

CVSS v3.1
9.8
EPSS
1%
Percentile
48.6
In the wild
Unconfirmed
What it is

🔥 A relaxed secret could give attackers the keys to your cookies! Without a strong `cookieSignatureSecret`, predicting or brute-forcing it is shockingly easy. ⚡ Think of it like a restaurant kitchen where each chef creates their own recipe for the house special without a shared, secret recipe. If one chef has a weak recipe, customers could get a counterfeit dish that ruins the dining experience. In this case, each Druid node generating its own weak secret leads to inconsistent and insecure authentication. An attacker could forge authentication tokens, allowing unauthorized access to your system — an absolutely devastating blow to your security. In distributed setups, this inconsistency can cause authentication failures across nodes, effectively locking you out of your own data!

Put simply

Think of it like a restaurant kitchen where each chef creates their own recipe for the house special without a shared, secret recipe. If one chef has a weak recipe, customers could get a counterfeit dish that ruins the dining experience. In this case, each Druid node generating its own weak secret leads to inconsistent and insecure authentication. The vulnerability in Apache Druid's Kerberos authenticator arises from using a non-cryptographic random number generator for the `cookieSignatureSecret` when not explicitly set, allowing predictability and brute-force attacks to succeed.

What to do

An attacker could forge authentication tokens, allowing unauthorized access to your system — an absolutely devastating blow to your security. In distributed setups, this inconsistency can cause authentication failures across nodes, effectively locking you out of your own data! To secure your Druid setup, immediately upgrade to version 35.0.0, which mandates setting a strong `cookieSignatureSecret`. Ensure all relevant configurations are in place to prevent authentication bypass, and check your cluster for consistency across nodes. You're on the right track to bolstering your defenses! Follow these steps, and security hero status: activated! 🛡️

The record
Technical detail
CVSS v3.1
9.8 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00611 · 48.6th percentile
Weakness
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Published
2025-11-26T08:50Z
EPSS history
Timeline
  • 26 NOV 08:50Z
    Apache Druid: Kerberos authenticaton chooses a cryptographically unsecure secret if not configured explicitly.
    cvelistv5