S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Aug 18, 2025

CVE-2025-27888 Scanner

Targets the Druid management proxy endpoint, allowing an attacker to forge requests to internal systems from the server.

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.2k
Times Used
continuous scan runs
5.5k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2025-27888
5.8
CVSSmedium
Exploitable remotely over the internet · low-privilege account sufficient.

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.

Attack Vector
Network
Privileges Req.
Low
User Interaction
A
Affected
Apache Druidby Apache Software Foundation
AFFECTED< 31.0.2SAFE ✓≥ 31.0.2
Updated Aug 22, 2026View on NVD →
Detail

Apache Druid is a high-performance real-time analytics database designed for fast queries on large datasets. It is commonly used by data engineers and analysts in industries like finance, e-commerce, and telecommunications to power dashboards and ad-hoc analytics. Druid ingests streaming and batch data, storing it in a column-oriented format optimized for aggregation and filtering. Its distributed architecture scales horizontally across clusters, handling petabytes of data with sub-second query responses. Organizations rely on Druid for use cases such as clickstream analysis, network monitoring, and fraud detection.

CVE-2025-27888 is a Server-Side Request Forgery (SSRF) vulnerability in Apache Druid. This flaw arises when the management proxy component processes user-supplied URLs without adequate validation. An attacker can craft a malicious request that tricks the Druid server into making HTTP requests to arbitrary destinations. The root cause is insufficient sanitization of input parameters that control the target URL, allowing the server to be used as a proxy to reach internal or external systems.

The vulnerability specifically targets the Druid management proxy endpoint, which is designed to forward requests to other services within the cluster. By manipulating the proxy's URL parameter, an attacker can force the server to send requests to any IP address or domain, including internal network resources like databases, cloud metadata services, or other sensitive systems. The exploit does not require authentication, making it accessible to any attacker who can reach the Druid management interface.

If exploited, this SSRF vulnerability can lead to severe consequences. An attacker could scan internal networks, access confidential data from internal services, or pivot to other systems within the organization's infrastructure. In cloud environments, the attacker might retrieve instance metadata, including credentials, leading to broader compromise. The high CVSS score of 8.9 reflects the potential for significant data breaches and lateral movement within the network.

Solution Advice
  • Upgrade Apache Druid to version 31.0.2 or later, which includes a fix for CVE-2025-27888.
  • Disable the Druid management proxy if it is not required for your deployment.
  • Implement strict input validation and sanitization for all URL parameters used in proxy requests.
  • Configure network firewall rules to restrict outbound traffic from Druid servers to only authorized destinations.
  • Use allowlists to limit the IP addresses and domains that the management proxy can access.
  • Regularly audit and review Druid configuration files for any insecure proxy settings.
  • Monitor Druid logs for unusual outbound requests that may indicate SSRF exploitation attempts.
  • Apply the principle of least privilege to the Druid service account to minimize potential damage from SSRF attacks.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.