# Apache Druid vulnerable to Server-Side Request Forgery, Cross-site Scripting, Open Redirect

Advisory record · `GHSA-2xcr-p767-f3rv`

- **Identifiers:** `GHSA-2xcr-p767-f3rv` · `CVE-2025-27888`
- **State:** Confirmed
- **Severity:** CVSS 5.8 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html) · [CWE-601](https://cwe.mitre.org/data/definitions/601.html) · [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md) · [Open redirect](https://agentprime.io/advisories/tag/open-redirect.md) · [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 20 Mar 2025
- **Updated:** 15 Jul 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Mar 2025, 12:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.druid:druid` (Maven): affected `<31.0.2 || >=32.0.0, <32.0.1`; fixed in `31.0.2`, `32.0.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Druid versions below 31.0.2, and versions from 32.0.0 before 32.0.1, are affected. An authenticated user can send a specially crafted URL through the Druid management proxy to redirect requests to an arbitrary server, which can enable cross-site scripting or cross-site request forgery. Upgrade to Apache Druid 31.0.2 or 32.0.1. Disabling the management proxy mitigates the issue, though some web console features will stop working.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.8 Medium, CVSS 4.0: `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`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.019, the 80th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2xcr-p767-f3rv)

## Sources

- [GitHub Advisory Database: GHSA-2xcr-p767-f3rv](https://github.com/advisories/GHSA-2xcr-p767-f3rv)
- [OSV: GHSA-2xcr-p767-f3rv](https://osv.dev/vulnerability/GHSA-2xcr-p767-f3rv)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-27888>
- <https://github.com/apache/druid>
- <https://github.com/apache/druid/releases/tag/druid-31.0.2>
- <https://github.com/apache/druid/releases/tag/druid-32.0.1>
- <https://lists.apache.org/thread/c0qo989pwtrqkjv6xfr0c30dnjq8vf39>
- <http://www.openwall.com/lists/oss-security/2025/03/19/7>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2xcr-p767-f3rv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2xcr-p767-f3rv/>. Everything for agents: <https://agentprime.io/llms.txt>.