Skip to main content
CVE-2025-59390VulnerabilityPublished Updated

CVE-2025-59390: Apache Druid · PRNG

Affects Apache DruidSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 35.0.0 as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 35.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade org.apache.druid/druid to 35.0.0.

Affected software

ProductAffectedFixed in
Mavenorg.apache.druid/druidpkg:maven/org.apache.druid/druidOther threatsAffected
  • <35.0.0
Fixed in
  • 35.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately audit their Apache Druid deployments to identify versions prior to 35.0.0 and verify if 'druid.auth.authenticator.kerberos.cookieSignatureSecret' is configured. The primary mitigation is to upgrade to Apache Druid 35.0.0 or later, which enforces mandatory strong secret configuration and disables fallback to weak PRNG. If immediate upgrade is not feasible, administrators must explicitly set a strong, cryptographically secure secret for 'druid.auth.authenticator.kerberos.cookieSignatureSecret' using a high-entropy random value generated by a secure PRNG (e.g., SecureRandom). Additionally, organizations should monitor authentication logs for anomalies indicative of token forgery or authentication bypass attempts. Network segmentation and strict access controls around Apache Druid nodes can reduce exposure. Finally, integrating multi-factor authentication and continuous security monitoring can help detect and prevent exploitation attempts.

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.

References

Community reviews

Loading reviews…