How severe is GHSA-wrqf-rrrw-w3mg?

GHSA-wrqf-rrrw-w3mg has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wrqf-rrrw-w3mg?

GHSA-wrqf-rrrw-w3mg affects the following packages: org.apache.druid:druid (Maven). Ecosystems affected: Maven.

How do I fix GHSA-wrqf-rrrw-w3mg?

Update org.apache.druid:druid to 0.20.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrqf-rrrw-w3mg is resolved across your whole dependency graph.

How do I detect GHSA-wrqf-rrrw-w3mg in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.druid:druid. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wrqf-rrrw-w3mg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wrqf-rrrw-w3mg?

O3 pinpoints whether GHSA-wrqf-rrrw-w3mg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wrqf-rrrw-w3mg actively exploited in the wild?

Yes. There are 14 known exploit references for GHSA-wrqf-rrrw-w3mg, including 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-wrqf-rrrw-w3mg?

GHSA-wrqf-rrrw-w3mg has an EPSS (Exploit Prediction Scoring System) score of 99.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for GHSA-wrqf-rrrw-w3mg?

A Nuclei detection template exists for GHSA-wrqf-rrrw-w3mg, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-wrqf-rrrw-w3mg published, and has it been updated?

GHSA-wrqf-rrrw-w3mg was published on June 16, 2021 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-wrqf-rrrw-w3mg

HIGH

Code injection in Apache Druid

Also known asCVE-2021-25646

Published

Jun 16, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

14 known

EPSS Exploitation Probability

via FIRST.org ↗

99.2%probability of exploitation in next 30 days

Very High Risk100th percentile-0.02%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.apache.druid:druid

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Druid includes the ability to execute user-provided JavaScript code embedded in various types of requests. This functionality is intended for use in high-trust environments, and is disabled by default. However, in Druid 0.20.0 and earlier, it is possible for an authenticated user to send a specially-crafted request that forces Druid to run user-provided JavaScript code for that request, regardless of server configuration. This can be leveraged to execute code on the target machine with the privileges of the Druid server process.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.druid:druid`	all versions	0.20.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.