GHSA-mw3v-mmfw-3x2g — opensearch-common
Fix: opensearch-project/OpenSearch#19491GHSA-mw3v-mmfw-3x2g is a CWE-674 vulnerability in org.opensearch:opensearch-common. A fix is available for org.opensearch:opensearch-common — see the affected versions and patch details below.
OpenSearch is vulnerable to DoS via complex query_string inputs
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mw3v-mmfw-3x2g.
EPSS Exploitation Probability
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.
Real-World Exposure
org.opensearch:opensearch-common☕org.opensearch:opensearch-commonReal-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
A vulnerability in OpenSearch allows attackers to cause Denial of Service (DoS) by submitting complex query_string inputs.
This issue affects all OpenSearch versions between 3.0.0 and < 3.3.0 and OpenSearch < 2.19.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opensearch:opensearch-common | ≥ 3.0.0&&< 3.3.0 | 3.3.0org.opensearch:opensearch-common:3.3.0 |
| ☕Maven | org.opensearch:opensearch-common | all versions | 2.19.4org.opensearch:opensearch-common:2.19.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opensearch:opensearch-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opensearch:opensearch-common to 3.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mw3v-mmfw-3x2g is resolved across your whole dependency graph.
Workarounds
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 O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mw3v-mmfw-3x2g can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mw3v-mmfw-3x2g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mw3v-mmfw-3x2g in your dependencies?
O3 Security finds GHSA-mw3v-mmfw-3x2g across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.