dbcve.org
DruidApplication · Apache

CVE-2025-27888

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-20
Fix available
A fix is available. Upgrade to 31.0.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Severity: medium (5.8) / important Server-Side Request Forgery (SSRF), Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Apache Druid. This issue affects all previous Druid versions. When using the Druid management proxy, a request that has a specially crafted URL could be used to redirect the request to an arbitrary server instead. This has the potential for XSS or XSRF. The user is required to be authenticated for this exploit. The management proxy is enabled in Druid's out-of-box configuration. It may be disabled to mitigate this vulnerability. If the management proxy is disabled, some web console features will not work properly, but core functionality is unaffected. Users are recommended to upgrade to Druid 31.0.2 or Druid 32.0.1, which fixes the issue.

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 management proxy (enabled by default) contains a flaw where specially crafted URLs can cause the server to redirect requests to arbitrary servers instead of the intended destination. This creates SSRF, open redirect, and potential XSS/XSRF attack vectors. The attacker requires authentication to exploit this vulnerability.

MitigationUpgrade to Druid 31.0.2 or 32.0.1 to receive the vendor patch, or alternatively disable the management proxy (though this will impair some web console features).

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:< 31.0.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify Apache Druid installation
    Look for running Java processes containing 'druid' in the command line, or search for directories containing 'apache-druid' or 'druid' in the filesystem
    Affected if Apache Druid software is present in the environment
  2. Determine installed Druid version
    Check the version file typically located in the Druid installation directory, or examine the druid-server JAR file name in the lib directory, or run: ps aux | grep druid to find the process and check its classpath
    Affected if The installed version number is lower than 31.0.2
  3. Verify management proxy is enabled
    Check runtime.properties or common runtime configuration files for the property 'druid.manager.enable' - if absent, the default is enabled. Alternatively, confirm the management port (default 8081/8091) responds to requests
    Affected if Management proxy is enabled (which is the default setting) and responds to requests
  4. Confirm network accessibility
    Verify the Druid web console and management ports are network-accessible from where the attacker would authenticate, typically ports 8081, 8090, or 8091
    Affected if The management proxy interface is reachable by an authenticated user who could craft malicious redirect URLs

The environment is affected if Apache Druid versions below 31.0.2 are running with the management proxy enabled (the default) and accessible to authenticated users.

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 31.0.2 or later
Fixed in 31.0.2
Interim mitigation

Upgrade to Druid 31.0.2 or 32.0.1 to receive the vendor patch, or alternatively disable the management proxy (though this will impair some web console features).

Recommended fix High confidence

31.0.2 or 32.0.1

  1. 1. Download Apache Druid version 31.0.2 or 32.0.1 from the official Apache Druid downloads page (https://druid.apache.org/download.html)
  2. 2. Stop all running Druid services and processes on your cluster
  3. 3. Create a complete backup of your existing Druid installation directory and all data directories (including metadata storage, deep storage, and segment caches)
  4. 4. Install the new Druid version to the same location as your existing installation, or to a new location if migrating
  5. 5. Review and migrate any custom configuration files (druid.conf, runtime.properties, etc.) from your previous installation to the new version
  6. 6. Start the Druid services in the correct order (ZooKeeper first, then brokers, coordinators, and historicals)
  7. 7. Verify that the management console is accessible and all services report as healthy
  8. 8. Confirm the upgrade by checking the Druid version in the web console under the 'Server' tab
Caveat Point upgrades within the same major version typically have minimal breaking changes; review release notes for any configuration or behavior changes

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

Fix this in Druid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27888 — 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-27888 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