Skip to main content
VulnerabilityPublished

CVE-2025-59390: Org.apache.druid:druid: Apache Druid’s Kerberos authenticator uses a weak fallback secret

Affects org.apache.druid:druidSource GCVE Database

0
Compare
Authoritative record:CVE-2025-59390· Critical 9.8

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

Data as of 19 Nov 2026, 02:44 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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. Weaponized: 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 18 Nov 2026.

What to do

Upgrade org.apache.druid:druid to 35.0.0.

Affected software

ProductAffectedFixed in
Mavenorg.apache.druid:druidAffected
  • <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

Upgrade Apache Druid to version 35.0.0 or later, where the vulnerability is fixed by requiring the explicit configuration of 'druid.auth.authenticator.kerberos.cookieSignatureSecret'. Services will fail to start if this secret is not set, preventing insecure fallback usage. Users should ensure to configure a strong secret for this setting. No other mitigations are indicated.

Description

Apache Druid versions prior to 35.0.0 have a vulnerability in the Kerberos authenticator where a weak fallback secret is used if the configuration 'druid.auth.authenticator.kerberos.cookieSignatureSecret' is not explicitly set. This fallback secret is generated using a non-cryptographically secure random number generator, ThreadLocalRandom, which may allow attackers to predict or brute force the secret used to sign authentication cookies. This can lead to token forgery or authentication bypass. Additionally, the fallback secret differs across processes, causing authentication failures in distributed deployments. Version 35.0.0 fixes this by requiring the secret to be set, and services will fail to start if it is not configured.

References

Community reviews

Loading reviews…