dbcve.org
DruidApplication · Apache

CVE-2025-59390

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-26
Fix available
A fix is available. Upgrade to 35.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Druid's Kerberos authenticator uses a cryptographically weak fallback secret (ThreadLocalRandom) when cookieSignatureSecret is not explicitly configured. This allows attackers to potentially predict or brute force cookie signatures for token forgery and authentication bypass. Additionally, each process generates its own secret, causing inconsistent secrets across distributed nodes and cluster authentication failures.

MitigationConfigure a strong, consistent druid.auth.authenticator.kerberos.cookieSignatureSecret across all cluster nodes and upgrade to Apache Druid 35.0.0 which enforces this requirement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DruidApplication
Affected:< 35.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Apache Druid version
    Check the installed Druid version by examining the release file or startup logs. Common locations: check the 'VERSION' file in the Druid installation directory, or look for version information in broker/indexer/coordinator logs on startup.
    Affected if Version is below 35.0.0 (any version < 35.0.0 is affected when other conditions are met)
  2. Identify if Kerberos authenticator is configured
    Search Druid configuration files (typically in conf directory) for any 'druid.auth.authenticator.kerberos' configuration blocks. Look for properties like druid.auth.authenticator.kerberos.authtype=kerberos or similar Kerberos-related authenticator settings.
    Affected if Kerberos authenticator is enabled and configured in the Druid configuration
  3. Verify cookieSignatureSecret is not explicitly set
    Search all Druid configuration files for the property 'druid.auth.authenticator.kerberos.cookieSignatureSecret'. Check if this property exists and has a value assigned. Also check for any environment variables or secret management configurations referencing this property.
    Affected if The property 'druid.auth.authenticator.kerberos.cookieSignatureSecret' is absent from configuration (not defined), which means the weak ThreadLocalRandom fallback secret is in use
  4. Check for inconsistent authentication behavior
    In a distributed Druid cluster, examine logs across multiple nodes (broker, coordinator, historical, indexer) for authentication failures or inconsistent session validation errors. Compare cookieSignatureSecret values across nodes if accessible in configuration.
    Affected if Authentication failures occur across nodes or session validation is inconsistent, indicating each process generated its own weak secret

A user is affected if they run Apache Druid version < 35.0.0 with Kerberos authenticator enabled AND the cookieSignatureSecret property is not explicitly configured, allowing the weak fallback secret to be used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 35.0.0 or later
Fixed in 35.0.0
Interim mitigation

Configure a strong, consistent druid.auth.authenticator.kerberos.cookieSignatureSecret across all cluster nodes and upgrade to Apache Druid 35.0.0 which enforces this requirement.

Recommended fix High confidence

35.0.0

  1. 1. Back up your current Druid configuration files, particularly the authentication/authorization settings.
  2. 2. Upgrade Apache Druid to version 35.0.0.
  3. 3. Configure `druid.auth.authenticator.kerberos.cookieSignatureSecret` in your Druid configuration with a strong, cryptographically secure secret value.
  4. 4. Verify the configuration is consistent across all nodes in distributed/multi-broker deployments.
  5. 5. Restart all Druid services to apply the changes.
Caveat Services will fail to start if `druid.auth.authenticator.kerberos.cookieSignatureSecret` is not explicitly configured in version 35.0.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Druid Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59390 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59390 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data