# CVE-2025-27888: Apache Druid: Server-Side Request Forgery and Cross-Site Scripting

> Authenticated attackers can exploit the management proxy to perform SSRF, XSS, or open redirects, potentially leading to code execution or security bypasses.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-2xcr-p767-f3rv

## What is CVE-2025-27888?

CVE-2025-27888 is a medium-severity server-side request forgery vulnerability in Apache Druid, published on 20 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-27888?

4 open source packages ship an affected version, including org.apache.druid:druid. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.druid:druid` | Maven | All versions | 31.0.2 |
| `org.apache.druid:druid` | Maven | All versions | 31.0.2 |
| `org.apache.druid:druid` | Maven | From 32.0.0 | 32.0.1 |
| `org.apache.druid:druid` | Maven | From 32.0.0 | 32.0.1 |

Products: Apache Druid.

## How do I fix CVE-2025-27888?

Upgrade org.apache.druid:druid to a fixed version for your release line: 31.0.2 or 32.0.1.

## Is CVE-2025-27888 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27888 exists.

Public exploit code:

- Apache Druid - Server-Side Request Forgery (nuclei): http/cves/2025/CVE-2025-27888.yaml

## Other vulnerabilities in Apache Druid

- [CVE-2026-23906](https://insights.sbomify.com/CVE-2026-23906/): Apache Druid: Authentication Bypass via LDAP Anonymous Bind (critical 9.8)
- [CVE-2025-59390](https://insights.sbomify.com/CVE-2025-59390/): Apache Druid: Kerberos authenticaton chooses a cryptographically unsecure secret if not configured explicitly. (critical 9.8)
- [CVE-2021-26919](https://insights.sbomify.com/CVE-2021-26919/): Apache Druid Authenticated users can execute arbitrary code from malicious MySQL database systems. (high 8.8)
- [CVE-2021-25646](https://insights.sbomify.com/CVE-2021-25646/): Authenticated users can override system configurations in their requests which allows them to execute arbitrary code. (high 8.8)
- [CVE-2024-45537](https://insights.sbomify.com/CVE-2024-45537/): Apache Druid: Users can provide MySQL JDBC properties not on allow list (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27888 and fix it if it is affected.

What it is: CVE-2025-27888 is a medium-severity server-side request forgery vulnerability in Apache Druid, published on 20 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27888 exists.

Affected packages and fixed versions:
- org.apache.druid:druid (Maven): affected all versions; fixed in 31.0.2
- org.apache.druid:druid (Maven): affected all versions; fixed in 31.0.2
- org.apache.druid:druid (Maven): affected from 32.0.0; fixed in 32.0.1
- org.apache.druid:druid (Maven): affected from 32.0.0; fixed in 32.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-27888/ (Markdown: https://insights.sbomify.com/CVE-2025-27888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27888
- OSV: https://osv.dev/vulnerability/CVE-2025-27888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-27888/
Summaries are generated and may contain mistakes; the official description above is the record.